Using NuGet to Distribute Our Company Internal DLLs
3 min read
3 min read
Releasing new software has to be simple and super fast! That was not the case for our company-internal class libraries till a couple of month ago until I finally decided to take the time to optimize that release process.
At the company where I'm working at currently, we have an internal class library which bundles a series of utilities with the scope of helping devs doing their day-to-day job. So far so good, however, there has always been a thing that puzzled me right from the beginning was the cumbersome release process of that library. Creating a release bundle consisted in
NuGet is a Visual Studio extension that makes it easy to install and update third-party libraries and tools in Visual Studio. When you use NuGet to install a package, it copies the library files to your solution and automatically updates your project (add references, change config files, etc.). If you remove a package, NuGet reverses whatever changes it made so that no clutter is left.The idea was to create a local, company-internal NuGet repository.
Tools > Library Package Manager > Package Manager Settings.
.nuspecfile for the class library and then a nice
publishRelease.batcontaining something like
msbuild Siag.Base.csproj /target:Rebuild /property:Configuration=Release
nuget pack Siag.Base.csproj -Symbols -Prop Configuration=Release
move *.nupkg \\snip\snip\NuGetRepository