-
Notifications
You must be signed in to change notification settings - Fork 31
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
.net 5.0 excessive dependencies #19
Comments
ow yes, this lib should also target .NET Standard 2 @schourode would a PR accepted for this? It isn't a large change |
@304NotModified Absolutely! |
--> #24 |
GitHub auto-closed this issue when I merged the pull request, but I believe we are not quite done yet, as the new build yet has to be pushed to NuGet. @304NotModified Is that something you would be up for helping with? It has been quite a few years since I last uploaded anything there, and I don't quite recall the process (which may also have changed since) 😑 |
@schourode sure, will try to respond with the steps in the next days |
@schourode It's basically drag and drop; download the file from the buildserver, login to nuget, click upload, and drag the file into the upload zone. :) All required form fields should be prepopulated from the Nuget metadata. Ensure to bump version number in the project file before. Previous releases did not use tags, but has some benefits. (There are some failure points, f.ex several times Nuget tightened their package validation rules, so had to make further changes before release) |
I think its better to publish from appveyor directly, its more transparent |
@schourode see steps here: #28 |
Release 1.0.4 has been published, including all of the changes from @304NotModified. I believe this release should address also the issue reported here, so I will close this one now. Let me know if this is misunderstood. Thanks a million, @304NotModified ! 👏 |
I went to install this on a .net 5.0 project that I'm working on, and the list of dependencies seems to be excessive. I guess this is because the package only targets .NETFramework and .NETStandard.
The text was updated successfully, but these errors were encountered: