Addin directive errors with non-standard nuget packages.

[phillipsj]

When trying to using NuGet packages that don't use the "lib/net45" content location with the AddIn directive, I am receiving the following error:

Could not find any assemblies compatible with .NETFramework, Version=v4.5.
Error:  Failed to install addin 'WinSCP'

How to recreate:

1. Add the following AddIn directive

   #tool nuget:?package=WinSCP

2. Run build.ps1 and receive the error.

There are several libraries that do not use the standards, this is just one example.

[phillipsj]

The work around is to pull it down as a tool and use the reference directive to pull it in.

[patriksvensson]

@phillipsj In this case your only option is using #tool with #r like you mention that you do. You will encounter the same problem in VS.

Unless the WinScp package author changes the package to conform to the standard NuGet conventions it's not much we could do about it at the moment :/

What we theoretically could do in the future, that might be usable for other packages, is to add a parameter to explicitly include files in a NuGet package.

#addin nuget:?package=Foo&ref=bar/baz.dll&ref=qux/bar.dll

[phillipsj]

@patriksvensson Now that sounds like a cool feature, that way users could "opt-in" to load those if you know they can use it.

[devlead]

Though, preferably with .NET Core hopefully soon going mainstream, ideally addins should use correct framework monikers.

[phillipsj]

@devlead @patriksvensson Cool, you all can close this if you want, its fine with me.