In a .csproj file, what is <None Include="..."> for?

How is

<None Include="C:\foo.bar" />

different from

<Content Include="C:\foo.bar" />

?

The MSDN article on the build action property explains the differences.

> None - The file is not included in the project output group and is not compiled in the build process. An example is a text file that contains documentation, such as a Readme file. > > Content - The file is not compiled, but is included in the Content output group. For example, this setting is the default value for an .htm or other kind of Web file.

One difference is how they get published; "None" items don't get included in a publish, "Content" items do; for example, on the "Application Files" dialog on the Publish tab.

I am not 100% sure (I read the MSDN description of Build Action property) but just copying that answer from MSDN to StackOverflow does not answer the question completely for me.

The difference of None and Content only has an effect on Web projects. For a command line project, WinForm project or UnitTest project (in my case) etc. None and Content have no different behavior.

MSDN: "project output group" or "Content output group" only terms used in a Web project, right?

In my situation, my MSBuild file had an ItemGroup for image resources that appeared as follows:

  <ItemGroup>
    <Content Include="Resources\image001.png" />
    <Content Include="Resources\image002.png" />
    <Content Include="Resources\image003.png" />
    <Content Include="Resources\image004.png" />
    <None Include="Resources\image005.png" />
    <None Include="Resources\image006.png" />
    <None Include="Resources\image007.png" />
  </ItemGroup>

While my project was building fine, this left me wondering why I had a mix of Content and None item type elements in my ItemGroup. This MSDN article (for Visual Studio 2010) gave me the guidance I was looking for:

> Note that when the resource editor adds an image, it sets Build > Action to None, because the .resx file references the image > file. At build time, the image is pulled into the .resources file > created out of the .resx file. The image can then easily be accessed > by way of the strongly-typed class auto-generated for the .resx file. > Therefore, you should not change this setting to Embedded > Resource, because doing this would include the image two times in > the assembly.

Resolution: With this guidance, using a text editor, I changed the Content item type elements to None.

Also, for an overview of MSBuild items, see this MSDN article.

I have a project that contains no compilable items (it stores html and javascript for jasmine unit tests).

One day my solution (that contained said project) stopped compiling saying "The target "Build" does not exist in the project".

I added an import to bring in the compiler, which worked fine on my machine but failed using msbuild on the build server.

<Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />

I then changed a line from

<None Include="SpecRunner.html" />

to

<Content Include="SpecRunner.html" />

and it worked on the build server as well.

Content files are not included in a build, but are included in a publish.

None files are not included in a build or publish, unless they are configured that way by you. For instance, a "Copy to Output Directory" setting of "Always" or "Newer", will cause them to be included in both a build and publish.

You need None in a template project file to include files you define in the .vstemplate otherwise they are lost in the creation & translation process. They get left behind in the temp folder it uses to build everything and then deleted shortly after.

In my case .Pubxml is one of those files among None list. It's not meant for solution building or as a static file for web project. But to publish the site to Azure, the configurations are present in this.

As per Microsoft article these are the major types we see among .csproj file tags:

> None - The file is not included in the project output group and is not > compiled in the build process. An example is a text file that contains > documentation, such as a Readme file. > > Compile - The file is compiled into the build output. This setting is > used for code files. > > Content - The file is not compiled, but is included in the Content > output group. For example, this setting is the default value for an > .htm or other kind of Web file. > > Embedded Resource - This file is embedded in the main project build > output as a DLL or executable. It is typically used for resource > files.