SharpDevelop will now open the readme.txt file in a NuGet package when it is explicitly installed or updated. The readme.txt file needs to be in the root directory of the package. If the NuGet package is being installed as a dependency of another NuGet package then the readme.txt will not be opened.
Adds support for the new .NET Core target frameworks: core50 - Target framework that is compatible with the Core CLR. dnx452 - DNX-based apps using the full 4.5.2 version of the framework dnx46 - DNX-based apps using the full 4.6 version of the framework dnxcore50 - DNX-based apps using the Core 5.0 version of the framework
Logic to check if the NuGet package is for the solution or for the project was not handling any exceptions that could be generated. For example if installing a NuGet package that supports the dnx framework, which is not currently supported in NuGet 2.8.3, the exception would not be caught because the try catch was at a lower level and not at the top level. Exceptions are now caught when checking the package to see if it is a solution level package when adding, removing or managing a NuGet package.
…ow handled centrally in DesignTimeProperties.cs. This fixes the following bugs: Bindings/Converters on the Visibility property was triggered and replaced the value set by OutlineNodeBase.cs. Changes on Visibility property ignored IsHidden setting, for example if IsHidden was true and changing Visibility to Visible would then make it Visible.
…dialog from another dialog.
…P6 it did not work
Adding a web reference to the following web service would fail since one of the schemas required a redirect to be downloaded. http://www.onvif.org/onvif/ver10/media/wsdl/media.wsdl
…operty Editors, they should not only Bind to the Value of the View, no they should also change the Properties of the underlaying DesignItem