Let me try to explain what I want to achieve and what goes wrong:
I'm trying to create a nuget package for a software library 'mylib.dll' that exist in a Silverlight and a .Net variant. The Silverlight variant has a dependency on an assembly 'some.required.lib.dll' in the Silverlight. The .Net variant of the library does
not have a corresponding dependency. This assembly is not available through a nuget package.
So, I created a directory structure where I put the Silverlight variant of 'mylib.dll' in the directory 'lib\sl4' and the .Net variant in 'lib\net40'.
Next, I created 'mylib.nuspec' and defined the dependency on 'some.required.lib.dll' as follows:
<frameworkAssembly assemblyName="some.required.lib" targetFramework="sl4" />
Now, when I try to install the nuget package created from this spec file, it complains that 'some.required.lib.dll' is not available for the 'net40' platform.
So, it looks like nuget tries to resolve the depenency on 'some.required.lib.dll'on the .net platform even though I've indicated explicitely that the dependency is only required for sl4.
Am I doing something wrong? Is this a bug? Or is what I want currently not possible?
Any help would be appreciated.