Folder lib/net35 is not created about nubuild HOT 6 CLOSED

There doesn't appear to be a reliable way of distinguishing references to the .NET 3.5 framework from .NET 2.0. As a workaround for 3.5 projects, you may have to include these libraries using the element in the nuspec instead of project references.

from nubuild.

Maybe to set default value to .NET 3.5 if no TragetFramework found would help, because in .NET 2.0 are not so many new applications.
And in case if some want to target .NET 2.0 he/she can do the work around you suggest.

from nubuild.

On other idea is to get that information from the visual studio dte object.

from nubuild.

You could also argue that the default should be .NET 2.0 if no TargetFrameworkAttribute is found in the referenced assembly. Feel free to fork the project and add set the folder name default there.

I'm not sure that going through the DTE would work when building through MSBuild. Thoughts?

from nubuild.

You can also set to .NET 2.0 :-) but i think either 2.0 or 3.5 should be set. (better then nothing)
And accessing dte durning build i alos do not know very well.
But to solve the problem reliable would be to write two small applications one wich is build with trageting framework 2.0 and one with 3.5. Then try to load the dll dynamically into both applications and if load succedd only in 3.5 application then you know ist 3.5 and if both succeed then you know it is 2.0. ;)

from nubuild.

The point is that arbitrarily setting the folder name to either would be incorrect for some use cases and would violate the principle of least surprise. I'd rather leave the target in the lib folder when the target framework can't be determined reliably.

from nubuild.