Why is the build: None action ignored for the * .cs file?

Question

I have a bad file in the project and I would like to save it. I know, I can use "Exclude from project", but this hides the file (in VS 2010, in VS 2008, it was still visible). But instead, I clicked on the properties Build Action: None. When I compile, the project compiles, but when I look in the list of errors, it still shows errors of this file.

Should the errors indicated in the report exclude file errors that were excluded from the assembly? Ie, tagged files are Contentnever built. But when the * .cs file Content, the errors in that file are still displayed in the error list. This is more than just a nuisance. In large projects, many errors and warnings arise from files that are never compiled, overshadowing the errors that matter. What can I do to prevent this?

Answer 1

The file is actually excluded from the assembly, but not from background compilation in the IDE, which creates errors in error list ¹ .

, Ctrl+A, , Ctrl+K, C, .

- . undefined:

#if DONTINCLUDE
...
//code goes here
...
#endif

, , , , , ... IDE, #, , .

^{1 _{, ( ), - ,}}