Bug 1761 - [New Resolver] Wrong position of semicolon caused by autoformatter
Summary: [New Resolver] Wrong position of semicolon caused by autoformatter
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: C# Binding ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Mike Krüger
Depends on:
Reported: 2011-10-28 08:00 UTC by Lluis Sanchez
Modified: 2011-11-04 03:51 UTC (History)
1 user (show)

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:

Description Lluis Sanchez 2011-10-28 08:00:57 UTC
Move the cursor to the end of a line that ends with a semicolon. Type an additional semicolon. The new semicolon is placed in a new line.
See http://screencast.com/t/MIr3nqq4.
Comment 1 Mike Krüger 2011-11-04 03:51:19 UTC
Should be fixed.

btw. that the semicolon is placed in a new line is not really a bug - when it's an empty statement it should be in a new line. However the behaviour in the screencast is a bug. That should never happen.