You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dotnet pack currently does nothing when invoked on an library project. We should be able to route dotnet pack invoked on the source project to the pkgproj and invoke its build target.
In addition to that it would be nice if the pkgproj build output doesn't point to the nuspec but to the nupkg instead (same what NuGet does). //update: already done by @ericstj: dotnet/arcade@b0b76b6
Long term, we should consider getting rid of pkgprojs and enable dotnet pack natively on our source projects. This probably involves extending the existing NuGet infrastructure, presumably with a new msbuild sdk similar to the existing Microsoft.DotNet.Build.Tasks.Packaging infra package. Related: dotnet/arcade#1033
See #37961 for exposing a single entry point for generating the library package.
dotnet pack
currently does nothing when invoked on an library project. We should be able to routedotnet pack
invoked on the source project to the pkgproj and invoke its build target.In addition to that it would be nice if the pkgproj build output doesn't point to the
nuspec
but to thenupkg
instead (same what NuGet does). //update: already done by @ericstj: dotnet/arcade@b0b76b6Long term, we should consider getting rid of
pkgproj
s and enabledotnet pack
natively on our source projects. This probably involves extending the existing NuGet infrastructure, presumably with a new msbuild sdk similar to the existing Microsoft.DotNet.Build.Tasks.Packaging infra package. Related: dotnet/arcade#1033See #37961 for exposing a single entry point for generating the library package.
cc @joperezr @ericstj @Anipik
The text was updated successfully, but these errors were encountered: