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.

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

Merge nuspec and CommonAssemblyInfo into csproj #1256

Merged
merged 17 commits into from
Jan 28, 2024

Conversation

scott-xu
Copy link
Collaborator

@scott-xu scott-xu commented Dec 2, 2023

Suggest using Nerdbank.GitVersioning after this PR

@scott-xu scott-xu marked this pull request as ready for review December 2, 2023 05:44
@Rob-Hague Rob-Hague mentioned this pull request Dec 2, 2023
4 tasks
@Rob-Hague
Copy link
Collaborator

Rob-Hague commented Dec 2, 2023

Will you also delete https://github.com/sshnet/SSH.NET/blob/develop/build/nuget/SSH.NET.nuspec?

(assuming this works well with sandcastle etc.)

@scott-xu
Copy link
Collaborator Author

scott-xu commented Dec 3, 2023

Will you also delete https://github.com/sshnet/SSH.NET/blob/develop/build/nuget/SSH.NET.nuspec?

(assuming this works well with sandcastle etc.)

I didn't delete the nuspec because I need confirmation from @WojciechNagorski.

@scott-xu
Copy link
Collaborator Author

scott-xu commented Dec 3, 2023

Regarding sandcastle, it would be good to migrate to docfx

@scott-xu scott-xu changed the title Generate nuget package when build Merge nuspec and CommonAssemblyInfo into csproj Dec 3, 2023
scott-xu and others added 2 commits December 5, 2023 07:13
@scott-xu
Copy link
Collaborator Author

scott-xu commented Dec 9, 2023

Will you also delete https://github.com/sshnet/SSH.NET/blob/develop/build/nuget/SSH.NET.nuspec?
(assuming this works well with sandcastle etc.)

I didn't delete the nuspec because I need confirmation from @WojciechNagorski.

@WojciechNagorski @drieseng , what do you think? Should we delete SSH.NET.nuspec?

@WojciechNagorski
Copy link
Collaborator

@scott-xu I'm sorry that the review is delayed, but I need more time to think and review it thoroughly.

@Rob-Hague
Copy link
Collaborator

It looks good. Before (using build/build.proj per the wiki):

image

After (using dotnet pack):

image

I think the next steps are:

  1. Delete the nuspec
  2. Modify build.proj to use dotnet pack instead of nuget.exe

Would it be possible to do these in this PR? That way we don't end up with two different ways to generate the release artifacts, and the new nuget method should integrate seamlessly into the current release process (which will also help with validation).

After that (in another PR) maybe we can call build.proj in CI to generate the artifacts.

@scott-xu scott-xu marked this pull request as draft January 7, 2024 02:08
@WojciechNagorski
Copy link
Collaborator

I will try to find time next week for this PR

@scott-xu scott-xu marked this pull request as ready for review January 28, 2024 10:00
@WojciechNagorski
Copy link
Collaborator

Hi I'm busy but I still remember about this PR.

Copy link
Collaborator

@Rob-Hague Rob-Hague left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice. Now we have source-link 🙂

msbuild /p:ReleaseVersion=2023.0.1 /t:Package:

image

@Rob-Hague Rob-Hague merged commit 323b514 into sshnet:develop Jan 28, 2024
1 check passed
@scott-xu scott-xu deleted the generate-nuget-package branch January 29, 2024 13:50
@WojciechNagorski
Copy link
Collaborator

This issue has been fixed in the 2024.0.0 version.

@WojciechNagorski WojciechNagorski added this to the 2024.0.0 milestone Feb 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants