Bug 9322 - Slow MonoDevelop and broke Intellisense because of "System does not exist in current context", but everything else works.
Summary: Slow MonoDevelop and broke Intellisense because of "System does not exist in ...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 3.0.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2013-01-07 10:32 UTC by Michele
Modified: 2013-01-07 14:28 UTC (History)
1 user (show)

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

photo of error (100.83 KB, image/png)
2013-01-07 10:32 UTC, Michele

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 Michele 2013-01-07 10:32:09 UTC
Created attachment 3167 [details]
photo of error

Using MonoDevelop, when I build my code and there's an error, any type of error, MonoDevelop reports an error also on "using System;" (cs0103: System does not exist in current context), and makes System red (also many other words go red), because of semantic highlight.
If I correct the code and build correctly the program, System remains red and Intellisense stops working.

Restart MonoDevelop and everything works.
Comment 1 Mike Krüger 2013-01-07 14:25:22 UTC
I think it's fixed in the next major version - I've rewritten the semantic highlighting.
Comment 2 Michele 2013-01-07 14:28:19 UTC
Thank you very much.