
Yesterday, the NuGet batch manager for the .NET platform received another update to version 1.7. The following are the innovations in the new version.
Support for package configuration at the solution level
With the release of NuGet 1.7, the package manager supports the configuration of packages not only for each project, but also for the solution as a whole. The package configuration file
packages.config can now be placed at the solution level in a special
.nuget folder. This new feature allows you to use the Package Restore feature at the solution level.
Prerelease package support in package manager GUI
In the package manager interface, it is now possible to filter and search for packages with the status of “pre-release”, that is, in the status of beta versions. Using the drop-down menu, you can tell the manager to select all packages, not just packages with stable versions.

')
Ability to restore packages in the project
If the packages in the project are configured with the support of the Package Restore function and in the case when the necessary files for the package are missing, the NuGet manager will notify you of the missing files and suggest repairing the affected package.

Exactly the same warning will be received by users of the command line of the package manager.

File readme.txt in the package
NuGet version 1.7 Now, by default, will open the text file readme.txt if it is found in the package structure. This will allow package developers to display important information about the package after it is installed.
New-Package Team
The New-Package team has been removed from the package manager. Developers are encouraged to use the nuget.exe command interpreter or the NuGet Package Explorer program with a GUI to create new packages.
Bug fixes and closed bugtracker entries
During the development of NuGet 1.7,
88 bugtracker entries were closed, some of which were package manager errors. Of the 88 entries, six were closed with the status of importance medium and two with the status High.