Options
Linqpad picks incorrect nuget target (netmf vs netstandard)
If I add a reference to a multitargeted nuget package that targets only .net microframework (netmf*) and .net standard (netstandard*), linqpad resolves assemblies from the .net microframework lib folder. For runtime compatibility this is almost certainly not what you want.
As a workaround package maintainers could build and include a full .net framework target for compatibility with linqpad. It would however be much nicer if linqpad was able to preference netstandard over netmf targets.
Poking around a little, it looks like LINQPad.Interop.NuGet.NuGetRepositoryRoot.FrameworkComparer could be tweaked to resolve this.
Here's a repro and suggested fix: http://share.linqpad.net/p9f3ia.linq
As a workaround package maintainers could build and include a full .net framework target for compatibility with linqpad. It would however be much nicer if linqpad was able to preference netstandard over netmf targets.
Poking around a little, it looks like LINQPad.Interop.NuGet.NuGetRepositoryRoot.FrameworkComparer could be tweaked to resolve this.
Here's a repro and suggested fix: http://share.linqpad.net/p9f3ia.linq
Comments
http://www.linqpad.net/download.aspx#beta