Previously if a solution level NuGet package, such as Fake, was
installed then running the Uninstall-Package cmdlet would not find
the Fake NuGet package and report an error. Now if the NuGet package
is not found in the project's package repository then the solution's
package repository is checked.
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.
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.
Matt Ward
Peter Forstmeier
Siegfried Pammer
Linquize
Daniel Grunwald
Christoph Wille
Andreas Weizel
jkuehner
gumme
gumme
jogibear9988