Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 3399 [details]
3 screenshots showing the issue in further detail.
Using both Linux (Xubuntu 12.10 x64, MonoDevelop 18.104.22.168) and Windows (Win7 x64, MonoDevelop 3.0.6), I have encountered a strange issue when using compiler directives and symbol definitions.
For example, on the Project Options -> Compiler -> Define Symbols, I have a symbol defined. LOGGING.
In the code, I have something like:
Logger.Something.Error("Some error message here");
With the symbol LOGGING defined in the compiler options for the project, it compiles as expected, the code doesn't get colored as a comment would (if the symbol wasn't defined in the compiler options), but if attempting to use autocomplete while typing the statement, the autocomplete doesn't appear to take into consideration the text I've already typed. Every time autocomplete triggers (like on a period, or parenthesis, etc), it does so as if I am starting a new line of code fresh, completely ignoring the currently in-progress statement being typed.
Also, the syntax highlighting only partially works, as shown in the screenshots
The bug has been fixed.
Fixed in what version?