Anyone else see this? Something to the effect of the below:
Reference Not Available
package version installed successfully.
I tried adding a reference to a Silverlight Project that is not for SL and watch it try to add it and then unreference it as it is not available for that project type.
But it doesn't clean up the packages.config. So NuGet believes that it is installed.
I have included a link to a download at the bottom so you can verify this behavior.
Steps to repro:
1. Create a silverlight project
2. Add a reference to automapper to it.
automapper has this structure
So the reference is not there, but I still have the package installed in that silverlight project. As an end user if the package install is not successful, I should not have it installed.
This seems like a bug to me. Didn't see any other notes in discussions, so I thought I would open this discussion.
Running on Win7 x64 SP1 - VS2010 Ultimate - NuGet 18.104.22.168