News

NuGet Package Manager Tweaked for Enterprise Customers in .NET 4.5.1

Microsoft adds a libraries feed that is as fully supported as the .NET Framework.

The .NET Framework just had its official update to version 4.5.1. Along with that update is a new effort by Microsoft to get NuGet, a package delivery system for Visual Studio, into the hands of more enterprise-level customers.

Microsoft has substantially tweaked NuGet in .NET 4.5.1 for better enterprise use, Alok Shriram, a Program Manager on the .NET Core Framework Team, blogged earlier this week.

"Some larger enterprise customers have been hesitant to adopt our NuGet releases, for a few different reasons. We believe that we've solved those issues in the .NET Framework 4.5.1."

Among the most persistent complaints from customers were that NuGet packages lacked discoverability, and a lack of package support. The answer for Microsoft was to create a  .NET NuGet libraries feed. The feed has the same level of support as the .NET Framework, according to Shriram. The feed, he blogged, is basically the same as regular .NET libraries, delivered via NuGet instead of only through a standard .NET Framework update.

The other major change for large customers is that the .NET Framework Microsoft Update servicing model has been extended to the NuGet libraries feed. One practical effect of the change is that security patches, for example, can be pushed through .NET NuGet assemblies with Windows Update, allowing for more timely fixes. Shriram noted that such support is only enabled for apps running on .NET 4.5.1.

The .NET NuGet feed shows up in Visual Studio the way it always has, but it's been enhanced in the just-released version Visual Studio 2013: a new item will appear in the NuGet client as "Microsoft and .NET". The client is also available as an update to Visual Studio 2012.

NuGet is a Visual Studio extension for managing libraries. When a developer installs a package, NuGet copies the necessary files to the solution and makes any needed changes, like adding references and changing app.config or web.config files. Some of the most popular packages include the Entity Framework, SignalR, Razor and the Web API. The packages come bundled as a .nupkg file.

NuGet runs on all versions of Visual Studio 2013, Visual Studio 2012 and Visual Studio 2010, as well as Visual Web Developer 2010 and Windows Phone Developer Tools 7.1. NuGet is supported on all Windows operating systems back to Windows XP SP3.

About the Author

Keith Ward is the editor in chief of Virtualization & Cloud Review. Follow him on Twitter @VirtReviewKeith.

comments powered by Disqus

Featured

  • Creating Reactive Applications in .NET

    In modern applications, data is being retrieved in asynchronous, real-time streams, as traditional pull requests where the clients asks for data from the server are becoming a thing of the past.

  • AI for GitHub Collaboration? Maybe Not So Much

    No doubt GitHub Copilot has been a boon for developers, but AI might not be the best tool for collaboration, according to developers weighing in on a recent social media post from the GitHub team.

  • Visual Studio 2022 Getting VS Code 'Command Palette' Equivalent

    As any Visual Studio Code user knows, the editor's command palette is a powerful tool for getting things done quickly, without having to navigate through menus and dialogs. Now, we learn how an equivalent is coming for Microsoft's flagship Visual Studio IDE, invoked by the same familiar Ctrl+Shift+P keyboard shortcut.

  • .NET 9 Preview 3: 'I've Been Waiting 9 Years for This API!'

    Microsoft's third preview of .NET 9 sees a lot of minor tweaks and fixes with no earth-shaking new functionality, but little things can be important to individual developers.

  • Data Anomaly Detection Using a Neural Autoencoder with C#

    Dr. James McCaffrey of Microsoft Research tackles the process of examining a set of source data to find data items that are different in some way from the majority of the source items.

Subscribe on YouTube