This is the same issue as https://connect.microsoft.com/VisualStudio/feedback/details/1244563/connect-roslyn-does-not-keep-property-bodies-on-single-line.

Oh yes, I knew I filed it somewhere, but was unable to find it! And given the VS is in RC and I am hitting it every day, I thought it might be worth mentioning it at GitHub.

This is exactly what @miloush claims. We go ahead and format the line on the typing of the ';' key, and the formatting engine has a rule that keeps the block on the same line if it is already on the same line, except is sees it as broken across two lines because the matching brace is on the next line (according to the parser). The reason this worked in prior VS was that we did not do any formatting after the semi-colon key if there were parse errors.

Still investigating possible solutions.

Not attempting to do formatting in the presence of parse errors sounds quite reasonable to me. In general I have to say that the IDE now feels rather aggressive (and the written code less 'stable') whenever there are parse errors.

Not attempting to do formatting in the presence of parse errors sounds quite reasonable to me.

I'd second this. I see invalid reformatting all over the place while editing code now. The editor can't wait until I'm done and constantly pushes things around in the wrong direction. If you don't want to disable this new "ability" completely, can there be at least an option in "Text editor; C#; Formatting; General"?

I noticed another weird behaviour of the VS 2015 editor. When pasting a line with #if something then all following #region ... and #endregion lines in the document are moved from their current indentation to the first column. Is this the same bug?

Actually, that looks like #2487.

@CyrusNajmabadi is going to think about this for a while

Fixed by #4644

Running Update 1 RC (24627) and it seems just the example above has been hotfixed. It still messes with e.g.:

namespace ConsoleApplication1
{
    class Program
    {
        public static bool One { get|

        static void Main(string[] args)
        {
        }
    }
}

and wraps it:

        public static bool One {
            get;

The same with:

public static void Test() { return|

I still think it is a good idea to avoid formatting (at least automatic) if there are parse errors.

If it helps, I have noticed that if you cancel the autocomplete suggestions of get/return it does not do it.

Hmm - the fact that it only happens if autocomplete is up means this is actually a different issue. Can you file something new to track it?

Running Update 2 CTP (25008) and still,

try { }
catch { continue|

gets wrapped as

try { }
catch {
    continue;

Is that a different issue? This one is not triggered by autocomplete.

This is a different issue.

OK, is that being tracked or should I create it?

You shoudl create it.