Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Switch from nuspecs to csproj to generate nuget packages #790

Open
Barsonax opened this issue Apr 20, 2020 · 0 comments
Open

Switch from nuspecs to csproj to generate nuget packages #790

Barsonax opened this issue Apr 20, 2020 · 0 comments
Labels
DevTool Area: Development tools and environment Discussion Nothing to be done until decided otherwise

Comments

@Barsonax
Copy link
Member

Barsonax commented Apr 20, 2020 •
edited
Loading

Summary

Currently we have a bunch of nuspecs to generate nuget packages. With sdk style project its also possible to do this from the csproj.

https://docs.microsoft.com/en-us/dotnet/core/tools/csproj#nuget-metadata-properties

Analysis

  • Automatically figures out dependencies and versions. For example when you have a project reference to a project with version 1.4.3 it will also be added to the nuget package.
  • Enables the use of dotnet pack
  • Easier multi targeting
  • Generally cleaner and less duplicate data.
  • Consider doing this after all projects are migrated to sdk style projects
@Barsonax Barsonax added DevTool Area: Development tools and environment Discussion Nothing to be done until decided otherwise labels Apr 20, 2020
@Barsonax Barsonax mentioned this issue Apr 30, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
DevTool Area: Development tools and environment Discussion Nothing to be done until decided otherwise
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Barsonax