Bug 1076 - Code completion failing for local properties in if statement
Summary: Code completion failing for local properties in if statement
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 2.8 beta 3
Hardware: Macintosh Mac OS
: Highest major
Target Milestone: ---
Assignee: Mike Krüger
URL:
: 492 ()
Depends on:
Blocks:
 
Reported: 2011-09-27 10:42 UTC by Chris Hardy [MSFT]
Modified: 2012-02-15 06:22 UTC (History)
4 users (show)

Tags: resolver
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:
Status:
RESOLVED FIXED

Description Chris Hardy [MSFT] 2011-09-27 10:42:14 UTC
See video: http://screencast.com/t/hdYbpqCRSjXo

Project to repo: http://dl.dropbox.com/u/90453/PhotoPicker.zip
Line 109 in OverlayViewController.cs

Hope this helps,

ChrisNTR
Comment 1 Mike Krüger 2011-09-28 03:26:43 UTC
Y, it's a bug in mcs - reported upstream.
Comment 2 Mike Krüger 2011-09-28 03:56:28 UTC
*** Bug 492 has been marked as a duplicate of this bug. ***
Comment 3 Alan McGovern 2011-09-30 09:36:52 UTC
Is this likely to get fixed for 2.8? If not, should we hold up the release for it?
Comment 4 Mike Krüger 2011-10-27 06:09:17 UTC
works in new resolver branch.
Comment 5 Chris Hardy [MSFT] 2012-01-07 12:35:28 UTC
This is still an issue in the 2.8.5 release and needs to be fixed for 2.8.*. Here's another video of the issue: http://screencast.com/t/KjLcM5ftZ
Comment 6 Mike Krüger 2012-01-09 01:54:00 UTC
Replacing the mcs in 2.8.* would have unexpected side effects - the mcs ast generation changed too much.
Comment 7 Joseph Hill 2012-01-09 08:29:27 UTC
What's the bug # in mcs?  I'm uncomfortable resolving a highest priority bug with no idea when or how the bug is actually going to be addressed for users?
Comment 8 Mike Krüger 2012-01-10 02:37:51 UTC
The bug is that mcs doesn't parse that. The bug is addressed, but the fix is not ready yet.

Mcs parsing changed too much & I'm not going to introduce destabilizing side effects in the 2.8.x line again. The last backport caused more harm than good. 

TBH that is not anywhere near a "highest priority" bug. This doesn't cause crashes or data loss in any way. 

I know that everyone wants their favorite bug fixed asap, but in the 2.8.x line only crashes/data loss bugs will get fixed on that layer. Replacing mcs would require investing some days in a backport which will cause side effects & maybe update even nrefactory ...

Setting that to "high".
Comment 11 Mike Krüger 2012-02-15 06:22:10 UTC
Fixed in 2.9.1/newresolver.