Is it possible to create any kind of project (old style or SDK-style) that will be responsible only to create nuget package but will not create addition assemblies for me.
Background of the story:
We have automation script that scan sln file and execute donet.exe pack for each project. By doing so we create number of the nuget packages with different assemblies.Now there is new consumer of our solution that require to deliver it with one single nupkg that should include all libraries, all assets (images, js, whatever), automation scripts to place it all over environment.
It seems that easiest way to achieve this goal is just to create addition csproj that will be responsible for this nupkg creation.So far I create something like this:
<Project Sdk="Microsoft.NET.Sdk"><PropertyGroup><TargetFramework>netstandard20</TargetFramework></PropertyGroup><ItemGroup><None Include="info.txt" Pack="true" PackagePath="\" /><None Include="AllContent" Pack="true" PackagePath="\all_my_application" /> ...</ItemGroup></Project>And as result I get the package with everything I need but also there is addition new dll in the lib folder.
Is it possible to configure project that will be used only for packaging purposes and will not produce any other artifacts?