I ran into this creating a console app from scratch because VS 2012 remembered the target framework from a previous app.
It is a negative scenario, but the package installs and adding the assembly references fails silently, which can be a bit confusing. I wonder if there is some NuGet metadata we are missing.
Comments: We got this from the NuGet team: > It might be because the content and tools files are not in subfolders for the target frameworks, resulting in us thinking they apply to any version. If you move the content and tools into “net40” folders, then I think you’ll get the behavior you expect. Also, about duplicating the files under Content and Tools: > If the contents for both net40 and net45 are the same, you only need net40
It is a negative scenario, but the package installs and adding the assembly references fails silently, which can be a bit confusing. I wonder if there is some NuGet metadata we are missing.
Comments: We got this from the NuGet team: > It might be because the content and tools files are not in subfolders for the target frameworks, resulting in us thinking they apply to any version. If you move the content and tools into “net40” folders, then I think you’ll get the behavior you expect. Also, about duplicating the files under Content and Tools: > If the contents for both net40 and net45 are the same, you only need net40