Nuget unable to install 1.6.0 in .Net Core 3.1 application about graphiot HOT 5 CLOSED

Hmm, I thought if I change the target to netstandard2.1 it will still support netcore3.1 and also others (like Mono and Xamarin). Perhaps I have to add it explicitly in the nuspec?

I'll have a closer look at that

from graphiot.

Ok, that was more complicated than I thought it would be. I could immediatelly reproduce it when creating a netcore3.1 console app, while working fine when referenced from netcore3.1 projects in the GraphIoT solution - meaning it has something to do with the compiled and packaged assembly in the nuget package.

I then figured I extend the project to multi target both netstandard2.1 and netcore3.1. This in turn does no longer work together with nuget pack then, but requires dotnet pack or msbuild -t:pack, both of which ignored my nuspec file. I could fix this also by referencing the nuspec in the project file - which then broke the variables in the nuspec file 😑. I found a github thread and working example of a prepoluation build step - et voilà!

Should be fixed with 78625e8 now.

I just published a new version 1.6.1 that should work again. Thanks for reporting!

from graphiot.

That sounds very familiar to what I had to do at work a while ago. Remeber the frustration with nuget pack vs dotnet pack... What github thread did you find?

from graphiot.

This one here: dotnetsdk/#5525

from graphiot.

Thanks and thanks for fixing it so quick!

from graphiot.