Produce outputs on build is removed from RC2 and PostCompile does not work as expected
See original GitHub issueIn RC1 (dnx) you could check the option “Produce outputs on build” which creates a NuGet after the build.
However in RC2 (dotnet) this does not work anymore, and the postcompile cannot be use for that.
I’ve defined this in my project.json:
"scripts": {
"postcompile": [ "dotnet pack --no-build --version-suffix %project:Version% project.json" ]
},
However this step is executed for every framework in my projoct.json ?
1> 0 Error(s)
1> Time elapsed 00:00:01.9413921
1> (The compilation time can be improved. Run "dotnet build --build-profile" for more information)
1> Project Linq.PropertyTranslator.Core (.NETStandard,Version=v1.4) will be compiled because project is not safe for incremental compilation. Use --build-profile flag for more information.
1> Compiling Linq.PropertyTranslator.Core for .NETStandard,Version=v1.4
1> Producing nuget package "Linq.PropertyTranslator.Core.1.0.2-1.0.2" for Linq.PropertyTranslator.Core
1> Linq.PropertyTranslator.Core -> C:\Projects\GitHub\Linq.PropertyTranslator.Core\src\Linq.PropertyTranslator.Core\bin\Debug\Linq.PropertyTranslator.Core.1.0.2-1.0.2.nupkg
1> Producing nuget package "Linq.PropertyTranslator.Core.1.0.2-1.0.2.symbols" for Linq.PropertyTranslator.Core
1> Linq.PropertyTranslator.Core -> C:\Projects\GitHub\Linq.PropertyTranslator.Core\src\Linq.PropertyTranslator.Core\bin\Debug\Linq.PropertyTranslator.Core.1.0.2-1.0.2.symbols.nupkg
1> Compilation succeeded.
1> 0 Warning(s)
1> 0 Error(s)
1> Time elapsed 00:00:01.9015257
1> (The compilation time can be improved. Run "dotnet build --build-profile" for more information)
1> Project Linq.PropertyTranslator.Core (.NETStandard,Version=v1.5) will be compiled because project is not safe for incremental compilation. Use --build-profile flag for more information.
1> Compiling Linq.PropertyTranslator.Core for .NETStandard,Version=v1.5
1> Producing nuget package "Linq.PropertyTranslator.Core.1.0.2-1.0.2" for Linq.PropertyTranslator.Core
1> Linq.PropertyTranslator.Core -> C:\Projects\GitHub\Linq.PropertyTranslator.Core\src\Linq.PropertyTranslator.Core\bin\Debug\Linq.PropertyTranslator.Core.1.0.2-1.0.2.nupkg
1> Producing nuget package "Linq.PropertyTranslator.Core.1.0.2-1.0.2.symbols" for Linq.PropertyTranslator.Core
1> Linq.PropertyTranslator.Core -> C:\Projects\GitHub\Linq.PropertyTranslator.Core\src\Linq.PropertyTranslator.Core\bin\Debug\Linq.PropertyTranslator.Core.1.0.2-1.0.2.symbols.nupkg
1> Compilation succeeded.
1> 0 Warning(s)
1> 0 Error(s)
1> Time elapsed 00:00:01.9287423
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Produce outputs on build is removed from RC2 and ...
However in RC2 (dotnet) this does not work anymore, and the postcompile cannot be use for that. I've defined this in my project.json:...
Read more >Missing "missing Produce outputs on build" option
After building the project, i used to get nuget package as output, but now in the build menu, we do not see the...
Read more >Solution-level `--output` option no longer valid for build- ...
Learn about a breaking change in the .NET 7.0.200 SDK where using the `--output` option is no longer valid when using a solution...
Read more >Ipq806x NSS build (Netgear R7800 / TP-Link C2600 / ...
As I have the torrent set, I have gone to make a transfer in lan, from my PC to the NAS and the...
Read more >Shrinkwrap - Arm
Shrinkwrap is a tool to simplify the process of building and running firmware on Arm Fixed Virtual Platforms (FVP).
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
postbuild is not working in RC2, it never gets executed whereas postcompile does
@StefH had this right 😃 Preview3 moves this behavior to csproj and lets us use msbuild for build orchestration. Pack itself is now a target, making this sort of chaining even easier.