News

NuGet 3 Nearing Completion

CTP 1 of the Microsoft development platform package manager introduces a new package source, speeds up performance and adds a debugger console.

Microsoft is nearing general availability of its NuGet 3.0, a package manager for its development platform tools that's part of the Visual Studio Extensions Gallery. Before that happens, the company is offering the first of a series of community technology previews (CTPs). This first CTP release introduces a new package source and speeds up performance. It also introduces a new debugger console.

The new package source is called "nuget.org (3.0.0-ctp1) preview," and, according to the blog post announcing the CTP 1, performance has been sped up a bit. The speed improvement is attributed in part to client requests being directed to Microsoft's content delivery network (CDN) to get data from storage, therefore bypassing the "v2 OData v2 endpoint on the server."

The blog also said some "under the hood changes" had to be made in order for development to progress on version 3. One such change was "drastic refactoring of the dependency resolver" to get it to resolve dependencies independent of the packaging process. The other was the interception and translation of API v2 requests (via a JSON intercept resource) to API v3 requests when a server implements API v3. The problem being solved here is that in the absence of an API v3 client (still under development), any request ends up appearing as if it were API v3 request, so "every single request the client makes ends up going against our API v3 Search Service and JSON-LD resources."

The other change is a new Package Manager Debug Console, included in the Visual Studio extension. As noted in the blog, Microsoft used the console to peer into the inner workings of the API v2-to-API v3 intercept process and its results.

Note that this version will work with Visual Studio versions 2013 and Visual Studio "14" only, for now: "We have always had a single extension that targets both of those versions, whereas we have a separate extension for Visual Studio 2013 and Visual Studio "14." NuGet 3.0 is now using some libraries that require .NET 4.5, and that would rule out updates for Visual Studio 2010."

NuGet 3.0 CTP 1 for Visual Studio 2013 can be downloaded here; for Visual Studio 14, it's here. Upon general availability in September, NuGet 3.0 will be available via the Visual Studio Extensions Gallery.

About the Author

You Tell 'Em, Readers: If you've read this far, know that Michael Domingo, Visual Studio Magazine Editor in Chief, is here to serve you, dear readers, and wants to get you the information you so richly deserve. What news, content, topics, issues do you want to see covered in Visual Studio Magazine? He's listening at [email protected].

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube