Hello,
I have a number of .NET Core console projects, and I’m working on how to get them packaged for deployment. In .NET 4.x, I would add a reference to octopack, but this doesn’t work in .NET Core projects. Are there any plans to update this tool? It’s normally not needed in the new dotnet.exe world, but there isn’t a way to pack .net console projects yet.
Thanks,
Erick
Hi Erick,
Will https://octopus.com/docs/guides/deploying-asp.net-core-web-applications help ?
Cheers
John
Thanks John. That is the approach that I am taking right now. It works fairly well for web projects, but much less so for console projects where the output of the publish is in N folders (one per framework/runtime combination built with).
The scenario is to have parity with Visual Studio publish on a console project (the publish settings xml is created/defined that expresses the runtime/framework). The result of this operation is a set of folders like:
/bin/debug/framework1/publish/
/bin/debug/framework2/publish/
And would like a package that contains
/framework1/
/framework2/
The story around publishing console applications seems a little up in the air, so this may not be feasible, but I believe that it is doable via msbuild (i.e., dotnet.exe msbuild …).
Thanks,
Erick
Hi Erick,
I think to achieve the structure you want you need to specify a nuspec file see https://docs.microsoft.com/en-us/nuget/schema/msbuild-targets#packing-using-a-nuspec.
Cheers
John