NuGet integration picks wrong framework variant in multi framework packages
I'm working with the LinqPad 5.44.02 at the moment. My script should use components from a NuGet packages that comes with two different frameworks in it (.NET4.5 and .Net Standard 2.0). In Visual Studio projects based on .NET 4.5 or even up to .NET 4.8 the variant for .NET 4.5 is choosen. With LinqPad the variant for .NET Standard 2.0 is used.
Im my case this causes that some features of the package can't be used as they are limited to the .NET variant of the library. Shouldn't the LinqPad use the same library selection algorithm than Microsoft has?