mirror of
https://github.com/quamotion/dotnet-packaging.git
synced 2026-02-14 21:32:52 +00:00
Current version (0.1.78) does not support netcoreapp2.2 #50
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @danielmoncada on GitHub (May 1, 2019).
Doing a nuget upgrade, I get the following error:
Note that version '0.1.70' works just fine
@qmfrederik commented on GitHub (May 2, 2019):
Sorry about that,
dotnet-debnow ships as a .NET Core CLI tool. This means you can remove the reference todotnet-*from your.csprojfile (you do have to keep the reference toPackaging.Targets, though).Then, do
dotnet tool install --global dotnet-deband rundotnet debfrom the command line.@danielmoncada commented on GitHub (Jul 2, 2019):
@qmfrederik thanks. Can you run the tool without having to do a 'tool install'?
@qmfrederik commented on GitHub (Dec 5, 2019):
@danielmoncada These tools are .NET Console applications, which do little more than invoking msbuild.
If you have a reference to Packaging.Targets in your project, you can just run
msbuild /t:CreateDebormsbuild /t:CreateRpm.You can also extract the binary from the NuGet package and deploy it yourself, if that's what you're asking. But you could also do
dotnet tool install --tool-path . dotnet-rpmto install the tool in your current working direcctory.Is there a specific reason you don't want to use
dotnet tool?@danielmoncada commented on GitHub (Feb 15, 2020):
@qmfrederik sorry for the late reply.
We are currently using CakeBuild to provide a custom build on our production server (without having to bother SCM for a new configuration). That way, if we want to configure or change the build process, we can just change our CakeBuild script.
dotnet tool means we will need to change the build server dependencies and not have as much control.