Nugets should not reference facade assemblies as framework dependencies

[HenrikFrystykNielsen]

Referencing System.IO and other facade assemblies in the nuget metadata fails on .NET 4.5.1 installations. Remove System.IO from the metadata:

<?xml version="1.0" encoding="utf-8"?>
<package xmlns="http://schemas.microsoft.com/packaging/2012/06/nuspec.xsd">
<metadata>
<id>Microsoft.AspNet.DataProtection</id>
<version>1.0.0-rc1-final</version>
…
<dependencies>
…
</dependencies>
<frameworkAssemblies>
_<frameworkAssembly assemblyName="System.IO" targetFramework=".NETFramework4.5.1" />_
<frameworkAssembly assemblyName="System.Security" targetFramework=".NETFramework4.5.1" />
<frameworkAssembly assemblyName="System.Xml" targetFramework=".NETFramework4.5.1" />
<frameworkAssembly assemblyName="System.Xml.Linq" targetFramework=".NETFramework4.5.1" />
<frameworkAssembly assemblyName="mscorlib" targetFramework=".NETFramework4.5.1" />
<frameworkAssembly assemblyName="System" targetFramework=".NETFramework4.5.1" />
<frameworkAssembly assemblyName="System.Core" targetFramework=".NETFramework4.5.1" />
<frameworkAssembly assemblyName="Microsoft.CSharp" targetFramework=".NETFramework4.5.1" />
</frameworkAssemblies>
</metadata>
</package>

[blowdart]

@Tratcher can you take care of this once the general renaming stuff has settled down?

[muratg]

@davidfowl said he has some ideas to make this better in @pakrym's PR above (which was closed without merging.) Moving to 1.0.0 milestone.

@davidfowl please elaborate what you're thinking and we'll assign it to someone.

[davidfowl]

This is already fixed in the latest packages