-
-
Notifications
You must be signed in to change notification settings - Fork 940
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
Conversation
IncludeSymbols
Will you also delete https://github.com/sshnet/SSH.NET/blob/develop/build/nuget/SSH.NET.nuspec? (assuming this works well with sandcastle etc.) |
Co-authored-by: Rob Hague <rob.hague00@gmail.com>
I didn't delete the nuspec because I need confirmation from @WojciechNagorski. |
Regarding sandcastle, it would be good to migrate to docfx |
Co-authored-by: Rob Hague <rob.hague00@gmail.com>
@WojciechNagorski @drieseng , what do you think? Should we delete SSH.NET.nuspec? |
@scott-xu I'm sorry that the review is delayed, but I need more time to think and review it thoroughly. |
It looks good. Before (using build/build.proj per the wiki): After (using I think the next steps are:
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. |
I will try to find time next week for this PR |
Hi I'm busy but I still remember about this PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This issue has been fixed in the 2024.0.0 version. |
Suggest using Nerdbank.GitVersioning after this PR