NuGet allows us to download and install packages to our solutions using the NuGet manager in Visual Studio (or from the command line using nuget.exe) from a remote server – for example, nuget.org. But what if you want to host your own packages locally or remotely (outside of nuget.org) for example due to workplace policies or simply not wanting to publish your own libraries to a public server.<\/p>\n
All the information contained in this post was gleaned from the references below. These are fantastic posts and I would urge anyone visiting this site to go and read those resources. What I want to do here is just distill things down to some basics to remind myself how to quickly and easily reproduce packages and spec for packages<\/em><\/p>\n Getting Started<\/strong><\/p>\n Let’s start of by creating a local (i.e. on your development machine) NuGet package folder. <\/p>\n At the point we now have Visual Studio set up to read from our packages folder – now we need to create some packages.<\/p>\n Creating a package<\/strong><\/p>\n So we need to create a nupkg file (which is basically a compressed file which includes binaries and configuration – change the extension to .zip and open with your preferred zip editor\/viewer to see the layout). This can be created using the Package Explorer GUI<\/a> or via a nuspec file and nugget.exe.<\/p>\n If you don’t already have it, download and install the command line version of NuGet which can be found here<\/a> see Command Line Utility. I placed mine in the folder I created previously, LocalPackages, as I will run it from here to work with the nupkg files etc.<\/p>\n As I prefer to let tools do the heavy lifting for me, I’ve downloaded the clickonce application, Package Explorer GUI<\/a>.<\/p>\n With the package explorer we can easily create nupkg files without a care in the world for what’s inside them :)<\/p>\n So let’s create a package very quickly using the Package Explorer GUI<\/p>\n If you now attempt to open this nupkg file, you’ll find it’s a binary file. If you prefer you can save the file as a nuspec (An XML file) via the GUI using the File | Save Meta data as… option and then when you are ready you can use<\/p>\n However you may well find that this fails because the assemblies added may need updating to the actual locations on your hard drive, so open the nuspc file and check the src paths. See the GUI made things easy.<\/p>\n Also when running the NuGet command line tool with Pack you may get a warning about the location of your assmebly, for example mine was by default stored in lib, but running the command line I find it is warning that I should move the file to a framework-specific folder.<\/p>\n For now we’ll not worry about this. Instead let’s see our nuget package being used.<\/p>\n Is our nuget package available<\/strong><\/p>\n We can now open Visual Studio (if not already opened) and assuming you’ve added your local package as outlined previously. <\/p>\n and you should see the package you created<\/li>\n<\/ol>\n Adding a local nuget package to our application<\/strong><\/p>\n or from the References folder on your solution, right mouse click and select Manage NuGet Packages, from Online, select your Local Feed and select your packages as normal and install<\/li>\n<\/ol>\n Remote Packages<\/strong><\/p>\n Check out the excellent post Hosting Your Own NuGet Feeds<\/a>. The section on “Creating Remote Feeds” get’s you up and running in no time at all. <\/p>\n But let’s list the steps anyway<\/p>\n That’s is for now.<\/p>\n References<\/strong><\/p>\n Nuspec Reference<\/a> NuGet allows us to download and install packages to our solutions using the NuGet manager in Visual Studio (or from the command line using nuget.exe) from a remote server – for example, nuget.org. But what if you want to host your own packages locally or remotely (outside of nuget.org) for example due to workplace policies […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[66],"tags":[],"class_list":["post-1508","post","type-post","status-publish","format-standard","hentry","category-nuget"],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/1508","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/comments?post=1508"}],"version-history":[{"count":5,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/1508\/revisions"}],"predecessor-version":[{"id":6851,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/posts\/1508\/revisions\/6851"}],"wp:attachment":[{"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/media?parent=1508"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/categories?post=1508"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/putridparrot.com\/blog\/wp-json\/wp\/v2\/tags?post=1508"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
\n
\r\nNuGet Pack MyPackageName.1.0.0.nuspec\r\n<\/pre>\n
\n
\r\nGet-Package -ListAvailable\r\n<\/pre>\n
\n
\r\nInstall-Package MyPackage\r\n<\/pre>\n
\n
\nHosting Your Own NuGet Feeds<\/a>
\nUsing A GUI (Package Explorer) to build packages<\/a>
\nCreating and Publishing a Package<\/a>
\nPackage Manager Console Powershell Reference<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"