- Space before "..." in menu items as common in German
- Improved uncommon cryptical abbreviations in status bar
- Improved wording and corrected writing in find-and-replace dialog by comparing with other text editors
Fixed null reference exception when package not found when
reinstalling a package for a single project.
Throw an exception when the package id cannot be found when
reinstalling a package for a single project or if the package id
cannot be found in any project when reinstalling for all projects.
A NuGet package can specify a dependency on another NuGet package when
a particular target framework is being installed:
<dependencies>
<group targetFramework="net40">
<dependency id="MyDependency" version="1.0"/>
</group>
</dependencies>
Installing this NuGet package into a project that targets net20 and
the MyDependency being unavailable on any NuGet feed should not fail.
Only installing the NuGet package into a project that targets net40
will this dependency be resolved.
NuGet.Core is updated to version 2.8.7 but NuGet.exe has only been
updated to version 2.8.6 since there has been no 2.8.7 version
released. The difference between 2.8.6 and 2.8.7 is one change to
how PowerShell is configured for Visual Studio which will have no
impact on NuGet.exe.
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.
h-h-h-h
Peter Forstmeier
Matt Ward
Siegfried Pammer
Andreas Weizel
jkuehner
Linquize