-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure to package on dotnet sdk > 3.1.102 #148
Comments
You can try this workaround: dotnet restore # first restore
dotnet deb --no-restore # then create the package |
Did not help. Ended up going to:
dotnet msbuild /t:CreateDeb /......
On 4/13/20 10:43 AM, Adan Jauregui wrote:
You can try this workaround:
dotnet restore# first restore
dotnet deb# then create the package
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#148 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJ2PT774WERBE5QZ64F53TRMMXKRANCNFSM4MCDB26Q>.
--
Drew Reis
|
Have similar problem on Win7 x64 (Russian)+Visual Studio 2019.
|
This seems to be a regression in .NET Core 3.1, see microsoft/MSBuildLocator#86 . Let's see if the workaround works. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Packaging seems to work when using dotnet msbuild /t:CreateDeb..... but NOT when running dotnet deb .....
dotnet deb runs fine on any dotnet 3.1 sdk <= 3.1.102, but any newer versions are throwing the following errors:
System Specs:
Ubuntu 18.04
Kernel 5.3.0-45-generic
dotnet version: 3.1.201
dotnet-deb version: 0.1.155+9e4041d64a
The text was updated successfully, but these errors were encountered: