Closed Issue: instructions in package are now ignored [2776]

I have a package who define a <references> assembly in the metadata of a nuspec. The definition is like the following :

<references>
<reference file="my.assembly.dll" />
</references>

I confirm the referenced dll is present in all platform present in the package (who are "lib/net45", "lib/NetCore45", "lib/sl4-wp71" and "lib/windowsphone8" in my case, with exactly the same name, even for lower/upper cases).

Until very recently, it was working correctly, but since what appears to be last nuget client update, the <references> node if not followed anymore and all assemblies in the "lib/<framework>" are referenced to my project. I tested with all supported platform and can confirm the same behavior.

I also discovered something interesting : if I go to the folder, I can see in packages/MyPackage.xx.x.x/ there's 2 interesting file : the package itself (.nupkg) and the extracted .nuspec file. If I open the nuspec file, I can see the <references> node is not present there! But.... if I open the .nupkg file and check fhe inner nuspec file, I can see the <references> node is as I configured it.

For some reasons, the <references> node is stripped when the nuspec file is unpacked from the package. That's weird!

As a final test, I open the original nuspec file using the last version of Nuget Package Explorer and I can see my referenced assembly in the "Filtered Assembly Reference" section, so the nuspec file seems correctly set.

Is it a bug ?
Comments: This is a known issue and we have fixed it in the upcoming 2.2 release.