Fix AutoMapper NuGet PowerShell scripts not being run.
A NuGet package can have install.ps1 and uninstall.ps1 PowerShell
scripts that target a particular framework based on the tools
subdirectory where they can be placed:
tools\net40\install.ps1
tools\net40\uninstall.ps1
Previously SharpDevelop would only look in the tools directory for
these scripts. Now it will use the project's target framework to find
the most compatible PowerShell install or uninstall script.
Note that NuGet does not support init.ps1 being target framework
specific and it will only be run if it exists in the tools directory
inside the NuGet package.
After this fix you can use the XamlDesigner also to Develop the XamlDesigner!!!
Before that we've had Bug's because of multiple loaded Assemblies with the same Name!
Running unit tests with code coverage would intermittently throw an
IOException:
System.IO.IOException: The process cannot access the file
'...OpenCover\coverage.xml'
(don't know if this should be Standart!)
(but I think it should be used on Paste from the Clipboard, so that Pasted Bindings work on Pasted Objects)
(not active at the Moment!)
- Remove unnecessary special ResourceDictionary wich handled when Key was not specified (now I specify always one)
- Find Properties and Events Not Only against the Instance also against the Element Type (This can be a different one, for Example ModernUiWindow instead of WindowClone)
- When Collection Instance is not set, create one (bug appeared in ModerUi ModernWindow)
- Parse of Frameworktemplates wich have References to Parent Resources (not yet App.Xaml Resources)
- Fixes in Xaml Parser (Attached Events, Attached Properties not always have both, a Setter and a Getter)
Siegfried Pammer
olegbevz
jogibear9988
gumme
Matt Ward
Daniel Grunwald
jkuehner
Andreas Weizel