Nuget packages with shaders in contentFiles are included as <Compile/> Instead of <Content/>

When I create a nuget package with a /contentFiles/any/netcoreapp3.0/ folder and add pixel and vertex shaders to the package (*.cso) which I want deployed at build time as content, I’m met with the following build error:

It appears it tries to include .cso as C# <Compile /> files, despite it is located in the contentFiles nuget package folder. If I add a .cso file directly to my solution, it’s default action is None, so there must be something wrt the nuget contentFiles folder related to this.

Repro step:

• Place a pixel shader in the /contentFiles/any/netcoreapp3.0/ folder of a nuget package, then try and use the package in a WPF .NET Core app.

Or just juse this repro app:

• ReproSample.zip
• Unzip, open solution and build.

/cc @rrelyea

[rrelyea]

On twitter you discussed a different problem, didn’t you?

[dotMorten]

@nguerrera Thanks Nick. I was slowly getting to that realization too 😃 I’d just expect it to pick Content as default and not C# Compile. It is after all called contentFiles