Bug 803 - Problems with auto completion and highlight
Summary: Problems with auto completion and highlight
Status: RESOLVED DUPLICATE of bug 709
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 2.6
Hardware: Macintosh Mac OS
: --- major
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2011-09-14 10:06 UTC by Llorenç Marti
Modified: 2011-09-15 03:01 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Llorenç Marti 2011-09-14 10:06:32 UTC
- With new version 2.6 (final) i have a lot of problems auto-completion, it turns my coding speed to 10 years ago. Sometimes and i dont know why, there are objects and classes that auto-completion fails completly to show its functions list. If i close the Monodevelop and I reload it ( and I am lucky) the next time all is ok.
Comment 1 Mike Krüger 2011-09-15 03:01:28 UTC
Can you give me concrete bug about where it fails ?

Can you try out the 2.8 beta 2 version, it contains some fixes for the intellisense speed issue ?
(even if it's called beta, it's more advanced than 2.6)

It seems that the speed may be a packaging problem - that bug is tracked elsewhere.

*** This bug has been marked as a duplicate of bug 709 ***