Xamarin Studio 5.1 was released last week and it includes some new features for the NuGet addin.
- Searching and installing a specific version of a NuGet package.
- Support for NuGet package sources defined in a solution specific NuGet.Config file.
More details on all the new features and changes in Xamarin Studio 5.1 can be found in the release notes. Now let us take a look at the new NuGet features.
Searching and installing a specific version of a NuGet package
The Add Packages dialog can now be used to search and install a specific version of a NuGet package. You can search for all versions, a range of versions, or a specific version of a NuGet package. To do this the following search syntax is used:
The packages are shown in the Add Packages dialog with the most recent version at the top. At the top right of each package in the package list you will see the package version instead of the download count allowing you to find the particular version you want to install.
To search for all versions of the AutoMapper NuGet package you can use an asterisk or leave the version number blank.
To search for all the 2.1 versions of the AutoMapper NuGet package you can use the search:
This will return a range of versions from 2.1.0 up to but not including 2.2.
The package id used in the search must match the id of the NuGet package otherwise no results will be returned.
Searching for package versions is also supported in the universal search at the top right of Xamarin Studio.
Package sources defined in a solution specific NuGet.Config file
If package sources are defined in the solution’s NuGet.Config file then these will be available in the Add Packages dialog when this solution is opened. The NuGet.Config file can be in the solution directory or in the .nuget subdirectory. An example NuGet.Config file is shown below.
<configuration> <packageSources> <add key="ASP.NET vNext - MyGet" value="https://www.myget.org/F/aspnetvnext/" /> </packageSources> </configuration>
When the solution is opened the package sources defined in the NuGet.config file are available in the drop down list at the top left of the Add Packages dialog.
Proxy credentials not being requested for a https package source.
Added a workaround to NuGet to handle Mono returning a different http response when proxy authentication is required.
Web.config transforms not being applied when installing NuGet packages such as Nancy.Hosting.Aspnet.
Projects were not being recognised as web projects so transforms were only being applied to app.config files.
XDT remove transforms (Xml Document Transformations) failing on Mono.
Modified the XDT library that ships with Xamarin Studio to handle different behaviour on Mono compared with Microsoft’s .NET Framework. These transforms are used in the Microsoft.AspNet.Mvc NuGet package.