The NuGet package manager has become the standard for developing software on the Microsoft platform including .NET and the NuGet Gallery emerged as a large public open source package repository. Sonatype Nexus, on the other hand, is the standard repository or component manager software running on servers from small open source projects and teams to multi-national companies from the Fortune 500.
Usage of a component manager for your binary packages is more and more understood as a default best practice…just like you use of a version control system for your source code. Build systems and other tools across different development platforms rely on solid package management solutions such as NuGet and usage of these tools only becomes efficient with the use of a component manager.
With the recent release of Nexus 2.9, our free Open Source version has full NuGet support included (Nexus Pro and CLM editions also support NuGet Packages). And adding Nexus into your development tools environment is easy. You can adopt Nexus in your environment with a quick download followed by a couple of minutes for installation and configuration:
- Download Nexus. Install Nexus on a Windows or Linux server, or for initial tests even just on your own development machine
- Configure a proxy repository for the NuGet Gallery
- Create a hosted repository to store your internally created and maybe proprietary NuGet packages
- Create a repository group that bundles the two repositories you just created and exposes them as one unit
- Configure Visual Studio and your command line tools to get all packages from the NuGet repository group provided by Nexus
Faster, More Reliable Builds
This initial setup will allow you to avoid repeated downloads from the NuGet Gallery since Nexus will proxy the components after the first download. You can host your packages (and potentially third party packages) on your own Nexus server and share them with your teams and CI servers.
Using Nexus you gain access to further benefits and improved understanding of your component usage like
- ability to host other proprietary packages in your own repositories or proxy other proprietary component manager repositories
- integrate Nexus via HTTP or the REST API and use it as package source for your QA and production deployments
- a user interface to manage the repositories and packages
- control of the user access via a security setup you can integrate with ActiveDirectory or other LDAP backends
- a search interface for finding available packages
- additional information about the packages including security vulnerability and license data
- Nexus Speaks Your Language
Nexus also supports other repository formats such as Maven, YUM, OBR or NPM that might be useful in your organization allowing you to avoid running a number of applications to solve similar problems.
It’s Time to Up Your Game
Using a package manager like NuGet combined with a component manager like Nexus leads to one common verdict: once you experienced using them and have enjoyed the benefits, you are never going to want to go back. Get started now.
Latest posts by Manfred Moser (see all)
- Integration with Nexus Repository 3 - June 8, 2016
- Sonatype Automated Deployments with Atlassian Bitbucket Pipelines - May 24, 2016
- Migrating to Nexus Repository 3 – Easy Peasy - May 11, 2016
- Puppet-eering the Nexus Repository Manager - May 2, 2016
- Impressions from DevOpsDays Vancouver 2016 - April 19, 2016