Closed jaz-ah closed 7 years ago
otherwise @bcuff my diff on this nuget update looks like:
Hmm... the NETStandard.Library packages shouldn't come in unless you're on a dotnetcore / dotnetstandard build. The version of nuget you're using to update the package may be confused about which dependencies it ought to take.
You could
I'm on VS2017, using the nuget3 api for fetching... I can manually install the package and see if that works, I just worry that i'll have to do this anytime any updates happen - haven't seen this in other nugets yet...
Okay, thanks for the info. I'll play with it and see if I can fix the package so it doesn't do that.
thx @bcuff let me know if you want me to test anything out for you.
@jaz-ah I just uploaded a new release that should fix the problem
yup works thx @bcuff !
I currently have a project that is based on .Net Framework 4.6.2 - when trying to upgrade this nuget from 2.1.4->2.3.3, I get a large list of dependencies which i believe are required for a project depending on .Net Standard but not for .Net Framework - is there any way to avoid injesting this large dependency list in my case? or do I update the nuget and then manually remove the dependencies that aren't required?