[Proposal] Allow setting projects meant to only be used to not compile code as Non applicable for building.

[AraHaan]

This is to avoid any CSC warnings about there being no code in the project (obviously there would be no code if we do not mean for the csproj to build anything except generating nuspec / providing our own nuspec to the .NET pack targets files in the .NET SDK (so we can use dotnet pack with it).

I am thinking of something similar to <IsPackable>/<IsPackable> for this to be something like:

• <IsBuildable>true/false</IsBuildable> (default true)
• <BuildSupported>true/false</BuildSupported> (default true)
• <Buildable>true/false</Buildable> (default true)
• etc.

[ghost]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[AraHaan]

cc @dsplaisted

[AraHaan]

It does say that NoBuild can be used to skip building on dotnet pack on the project with nuspec, however what if I am running dotnet build to build other projects in the solution that just so happens to have the project with the nuspec only.

[dsplaisted]

Is this what you are looking for? https://github.com/microsoft/MSBuildSdks/tree/master/src/NoTargets

[AraHaan]

Oh that looks to be similar.

[kasperk81]

<IsPublishable> doesn't publish
<IsPackable> doesn't package

there should be a <IsBuildable> property which will skip the build. it should be a property like the other two so we can use Condtion=whatever on it. NoTargets is not it

[osexpert]

Missing this as well. Currently a problem if having sln with different projects, some eg. net8.0, some net8.0-windows. Can control dotnet publish, but not dotnet build, so had to split out a subset sln with only net8.0 projects.

<IsBuildable> would have allowed me to keep the original sln as-is and only set to true in Directory.Build.props if building for win-* and target framework is *-windows