We announced that Nexus Professional added support for .NET and NuGet repositories, but I wanted to reiterate that message by supplying some very detailed instructions to walk you through the process. NuGet has quickly become the defacto way to install libraries in Visual Studio, and, in some ways, the IDE integration between Visual Studio and NuGet Gallery puts integration between Maven and Eclipse or IntelliJ to shame. The Outercurve Foundation and Microsoft have created a really compelling GUI for discovering and integrating new OSS components.
If you’ve downloaded Nexus Professional 2.0 to start using or evaluating support for .NET and NuGet packages. Here are the steps you need to take to get started. (Don’t have Visual Studio, but you are still interested in exploring this feature? You can download Visual Web Developer 2010 Express and get started).
First, know that Nexus Professional doesn’t ship with any NuGet repositories pre-configured. The overall process for starting to proxy NuGet Gallery is to configure the required repositories on Nexus, group them into a single repository group, and then configure Visual Studio to read from Nexus. To start proxying NuGet Gallery follow these How-tos in order:
- Step 1. Create a Proxy for .NET components in NuGet Gallery
- Step 2. Create a Hosted Repository for .NET Components in Nexus Pro
- Step 3. Create a Repository Group for .NET Components in Nexus Pro
- Step 4. Install NuGet in Visual Studio
- Step 5. Configure Visual Studio to Download NuGet Libraries from Nexus
This process is also captured in a shareable Bit.ly Link Bundle walking you through the same collection of related How-tos.