Your official information source from the .NET Web Development and Tools group at Microsoft.
The NuGet packages for ASP.NET MVC 5.2, ASP.NET Web API 2.2 and ASP.NET Web Pages 3.2 are now live on the NuGet gallery!
Download this release
You can install or update the NuGet packages for ASP.NET MVC 5.2, ASP.NET Web API 2.2 and ASP.NET Web Pages 3.2 using the NuGet Package Manager Console, with the following commands:
Prerequisites for this release
What’s in this release?
This release primarily includes great new features for Web API OData v4 as summarized below but has bug fixes and minor features that bring in a lot more goodness to MVC, Web API, and Web Pages:
ASP.NET MVC 5.2
ASP.NET Web API 2.2
ASP.NET Web Pages 3.2
You can find a complete listing of the features and fixes included in this release by referring to the corresponding release notes:
Tutorials and other information about this release are available from the ASP.NET web site (http://www.asp.net).
Questions and feedback
You can submit questions related to this release on the ASP.NET forums (MVC, Web API, Web Pages).Please submit any issues you encounter and feature suggestions for future releases on our CodePlex site.
Thanks and enjoy!
MVC and Web API are (for the most part) a pleasure to use, thanks for all the work.
Cool. can you explain to me why a release like this does not mean an update to the main dotnet framework?
ASP.NET MVC, Web API and Web Pages ship as out of band NuGet packages - no .NET Framework update required. You just install the NuGet packages into your project which adds the right assembly references and you are good to go!
"Install-Package Microsoft.AspNet.WebApi -Version 5.2.0"
Is that a typo? Should it be "Install-Package Microsoft.AspNet.WebApi -Version 2.2.0"?
Well, that's confusing (nothing new): according to "Manage NuGetPackages" Microsoft ASP.NET Web API 2.2 *is* Version 5.2.0 (no typo above).
I'm sure there is a semi-logical explanation for "2.2 == 5.2.0", but it is still confounding, confusing, and seemingly contradictory (not to be confrontational, but that's my take on it).
Yes, the packages for Web API 1.0 were actually versioned as 4.0, thus causing this versioning disconnect. In ASP.NET vNext (http://www.asp.net/vnext) we plan to merge MVC, Web API and Web Pages into a single framework - MVC 6. The versions will all get aligned at that time.