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).
- Getting the correct namescope for RootItem (the INameScope case was not checked).
- Clears the local namescope for the object if it exists, otherwise name changes will be registered in the local namespace instead of RootItem document namespace.
- Only adds _Copy (or CopyX, where X is an integer) if the previous name did not already end with _Copy. This prevents names as "myname_Copy_Copy_Copy..." to occur when copying and pasting already copied elements.
- Registers the new name to the RootItem namescope, only setting site.Name is not enough as its not yet a part of the RootItem document namescope.
Previously you could move an element that was hidden by hovering the cursor on the edges of the hidden control, and clicking when you saw the move-cursor appear.
Only shows the adorner panel if the parent component is visible.
If component is a ContentControl it must be of type ContentControl specifically, and not derived types like Label and Button where the added border is not wanted.
If component is a Border the adorner border is only drawn on the edges that is invisible.
The adorner is only created the first time it is added to adorners collection.
Matt Ward
Daniel Grunwald
Siegfried Pammer
gumme
Christoph Wille
mathiassimmack
jkuehner
jogibear9988