Bug 12332 - Line after #if removed due to message bubble
Summary: Line after #if removed due to message bubble
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Text Editor ()
Version: 4.1
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: 4.0.9 (from master)
Assignee: Mike Krüger
Depends on:
Reported: 2013-05-21 19:00 UTC by Paul Johnson
Modified: 2013-06-24 16:18 UTC (History)
1 user (show)

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

Video of bug in action (499.91 KB, application/x-shockwave-flash)
2013-05-21 19:00 UTC, Paul 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 Paul Johnson 2013-05-21 19:00:06 UTC
Created attachment 4005 [details]
Video of bug in action

(this is for version 4.0.8 - beta channel, though it happens as well on the stable version)

Say you have the following

private void foo()

if you want to put a #if / #endif conditional around either line, a bubble appears below the #if for the autocompleter. If you go to the end of the line beneath the #if and press return, the bubble and line is removed.

The video attached to this bug demonstrates it.
Comment 1 Mike Krüger 2013-05-24 05:44:27 UTC
Comment 2 PJ 2013-06-24 16:18:35 UTC
This bug was marked as fixed for Xamarin Studio 4.0.9, which is currently in the beta channel. Try it out!