Create your own local cloud how to#

Now that we've got a NuGet server up and running locally, let's deploy it to Windows Azure. (Please make sure to use a different key than the one given in this example). To ensure only authorized users will be able to add and delete packages, set requireApiKey to true and set apiKey to the specific key you want to use. Open up web.config and review the following settings. There's just one more thing to do before we can run and deploy our code, which is to review our configuration. Press F6 and ensure the solution builds successfully. Search for NuGet.Server and click Install. Right-click on References and select Manage NuGet Packages. Now, we'll use the official NuGet repository to add NuGet.Serverto our project. The Solution Explorer should show an empty solution, as follows: From the templates, select ASP.NET Empty Web Application, as follows: If you don't have one yet, you can sign up for a free 30-day trial here. Pre-requisitesĭo I need to mention you need Visual Studio? Maybe not, but I've just done it! Any recent edition should do (screenshots for this article are taken from Visual Studio 2013).Īnd obviously, you'll also need a valid subscription to Windows Azure.

Create your own local cloud how to#

This article will show you how you can create your own private NuGet server and how to host it in Windows Azure. If you regularly use NuGet Package Manager from Visual Studio, then you are already very familiar with the concept. NuGet packages also allow you to have multiple versions of a same package and to specify any eventual dependencies. One neat way of doing it, is to create packages, to store them in a repository and to reference them whenever needed. Whether you are part of a large development team or working alone on your own side project, you'll probably want to re-use code across multiple projects.