Enumerating the EnvDTE.Project.Object.References in a different app domain
was trying to load the PackageManagement assembly and failing. Changed
EnvDTE.References so it only exposes types in the SharpDevelop.EnvDTE assembly
and switch to using IEnumerable on the EnvDTE.References class.
Updating to a new NuGet package or installing a new NuGet
package with the old one still installed would leave the
old unused NuGet package in the packages folder.
NuGet packages that were still in the packages folder but
not installed in any projects are now not shown in the
Installed tab when managing NuGet packages for the solution.
The Fody NuGet package has an install PowerShell script that
directly updates the MSBuild project from the
Microsoft.Build.Evaluation.ProjectCollection.GlobalProjectCollection
to set a FodyPath property that defines where the Fody.targets
file should find the main Fody assembly.
Extended the support added for the Microsoft.Bcl.Build NuGet package
so project properties added by directly updating the MSBuild project
from the GlobalProjectCollection are added/updated in the actual
project file.
No support for updating properties that exist multiple times inside
a project (e.g. OutputPath).
Run uninstall PowerShell scripts before the NuGet package is
removed so the jQuery uninstall.ps1 script can find the Scripts
folder in the project when uninstalling.
The list of packages now shows the package title so
the package id is shown as a hyperlink on the right
hand side of the Manage Packages dialog when the
package is selected.
References to assemblies in a project that use the qualified assembly name, such as:
"NUnit.Framework, Version=2.6.2.0, Culture=neutral, PublicKeyToken=8cc8392e8503e009"
were not being removed and re-added when installing a NuGet package that included
that reference.
Add projects to MSBuild's global project collection if
the NuGet package has PowerShell scripts.
Add/Remove MSBuild project imports added to a project
held in MSBuild's global project collection after
the NuGet package has been installed.
Updated packages were not being displayed in the
Manage Packages dialog when the solution was selected
and two or more projects had the same NuGet packages but
different versions.
http://nuget.codeplex.com/workitem/3034
Matt Ward
Daniel Grunwald
Siegfried Pammer