Net45

@SimonCropp i was going through the NuGet docs and this caught my eye: http://docs.nuget.org/docs/reference/nuspec-reference#DLLs_for_different_frameworks when looking through the UrbanBlimp NuGet build i noticed the files where being placed into the folder lib\net40. At this point I looked to see what framework version was being targeted as I thought it was 4.5. Which it is.

I first thought of making a minor change so the folder would be updated to lib\net45 which would correctly identify the targeted framework. Then I had a second thought of well why not build assemblies for 4.0 and 4.5.

I added two new build configurations for NET40 and NET45 based on the Release configuration. Then I made some changes to the NuGet project so it could make the package correctly with a 4.0 framework targeted assembly being added to lib\net40 and a 4.5 framework targeted assembly to lib\net45. This looks to be working well.

The only pain points that i can can see is when building a new NuGet package, using Visual Studio, the solution will need to build with both NET40 and NET45 build configurations. Then the NuGet project can be built and the new NuGet package would be created.

If there's automation via CCNet or TeamCity then the three projects could be build in sequence NET40, NET45, then NeGet. Which would make it pretty easy.

Take a look and let me know what you think.

thanks,
@iamcharliegoddard