Bug 8618 - Intellisense broken within compiler directives
Summary: Intellisense broken within compiler directives
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: 3.0.x
Hardware: PC Windows
: Low normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2012-11-27 14:19 UTC by Justin Johnson
Modified: 2012-11-28 06:37 UTC (History)
2 users (show)

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

Demonstrates the different test cases (85.34 KB, image/png)
2012-11-27 14:19 UTC, Justin Johnson

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 Justin Johnson 2012-11-27 14:19:58 UTC
Created attachment 3022 [details]
Demonstrates the different test cases

Version: 3.0.5, note that I noticed this while working on a MfA project but it happens in C# POCOs.

Intellisense/Autocomplete is partially broken within compiler flags/directives.
If you create a compiler directive within a method, intellisense will be broken in these cases:

- method arguments and class members are detected and displayed in intellisense
- local-scope arguments, defined within the method, are not detected
- intellisense doesn't exist for member properties

Example screenshots attached.
Comment 1 Mike Krüger 2012-11-28 05:00:38 UTC
Then DEBUG isn't defined - I can only reproduce this behavior in RELEASE mode - in DEBUG mode it's wrong.

(however it's still a bug)
Comment 2 Mike Krüger 2012-11-28 06:37:12 UTC