Can i stop visual studio 2015 putting compiler directives against left margin?

Question

0.00/5 (No votes)

See more:

Hi,

I can almost hear the clamour of criticism from here, but I'm working alone and I have always found compiler directives much easier to read when they are placed at the same indent level as the code they are affecting. In older versions of Visual Studio, it left them where I put them, but 2015 insists on moving them whenever the file is formatted.

Does anyone know of a plugin or setting that will let me keep them where I like them?

Kind wishes ~ Patrick

PS - Please note, if I were working in a team, I would of course follow whatever convention the team had decided upon.

What I have tried:

I've turned off Options | C# | Formatting | General | Automatically format statement on ; } and paste

Posted 23-Feb-16 5:37am

Patrick Skelton

Updated 23-Feb-16 6:05am

v3

Add a Solution

Comments

Philippe Mori 23-Feb-16 19:26pm

Compiler directive should always be at left margin except for some case like #region.

However, in Visual Studio 2015, that kind of stuff is someone broken. In particular, Visual Studio 2015 will sometime mess code after pasting something like #if something. New editor based on Roslyn seems to ignore the fact that human write code from left to right and sometime insert code into existing code.

Report the problem to Microsoft using the tool in the upper right corner.

Although there are some options, from what I've heard they are also broken in some case. Thus, presently all options seems to not always work properly.

In some case, you can prevent Visual Studio to mess up code by writing code "backward" or using some other tricks while editing. If one notice the problem immediatly, he might undo its change. However, when affected code is outside of visible code, one have to fix code manually.

Part of the problem is that the new editor make some change to early. For example, it will reformat code as soon as one write # no even yet knowing if it will be #if, #region or something else.

Patrick Skelton 24-Feb-16 5:19am

In these days of colour-coding editors that take account of which compiler directives are active, I don't actually see the need to stick to the ancient notion that compiler directives should always go against the left margin, but that's a subject for another thread.

Thank you very much for the information.

Kind wishes ~ Patrick

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Accepted Answer · 2016-02-23T06:05:00

Solution 1

There is nothing built into Visual Studio that will turn that off and the edit document formatter does not apply indenting to directives. I don't know of a plugin that puts the indenting in or maintains it.

Posted 23-Feb-16 6:05am

Dave Kreskowiak