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:
This process is also captured in a shareable Bit.ly Link Bundle walking you through the same collection of related How-tos.
John K. Waters from VisualStudio magazine wrote a piece about the .NET support recently released with Nexus 2.0. Read it online. Many of our existing customers have told us that development is becoming increasingly heterogeneous with Java and .NET forming the bulk of most enterprise development efforts. With Nexus you have a single place to integrate: a single place to publish artifacts and consume OSS.
Here’s the key quote from Brian Fox:
“The .NET world is kind of where the Java world was five years ago,” said Brian Fox, Sonatype’s vice president of engineering. “It’s just discovering the importance of a centralized management facility for sharing binary components. There is no great solution for sharing .NET components out there right now. Developers share them via source control systems or file systems, but there’s no analog to a repository manager in .NET. Until now.”
To learn more about Nexus Pro 2.0, visit http://www.sonatype.com/nexus.
While we released Nexus Professional 2.0 last week, today we’re officially announcing our support for .NET. Here’s a key excerpt from today’s press release:
Sonatype, the company that is transforming software development, today announced that software developers using the .NET Framework can now utilize the Sonatype Nexus Professional repository manager to store, access and manage .NET components. Nexus is already the industry’s most widely used repository manager for Java components. By extending support to .NET, Sonatype now offers an ideal solution for Microsoft development teams, as well as heterogeneous development organizations.
Nexus Professional 2.0 supports NuGet repositories, and while you’ll hear much more about that next week I think it’s important to introduce what NuGet is before we introduce you to how Nexus supports it. NuGet and NuGet Gallery is a relative newly way for .NET developers and .NET open source projects to distribute binaries. Nexus provides first-class support for proxying, hosting, and grouping the NuGet package repository format.
Now, I understand that the bulk of our audience is comprised of Java developers, and when a Java developer sees a .NET announcement or feature fly by it’s often met with a shrug. For whatever reason, there’s almost no overlap between Java developers and .NET developers, so I think it’s important to talk about NuGet in terms Java developers can understand. I also think it’s important for people to realize just how interested Sonatype is in spreading the word about NuGet. NuGet and NuGet Gallery remind us of Central, and if you’ve been paying attention to my blog posts in particular, I’m convinced that Central transformed both the way Java developers consume artifacts and the rate at which open source innovation happened over the last decade.