Build your own NuGet server and nuget

Build your own NuGet server and nuget

Preface:It is much easier to manage NuGet references, especially when it comes to teamwork. However, during the use process, it is found that the process of restoring the package remotely is simply a thank-you. No way, I had to create an NuGet server myself.

--------------- I am a split line ------------

Start with the question:

1. Deploy NugetServer

1. Create an empty web Project (here, 4.6 is selected for the. NET Framework version because the latest stable version 3.0.0 of the next NuGet. Server package depends on. NET Framework 4.6)

2. Add the NuGet. Server package for the project

3. Publish the website to IIS on the server. When you access the website, you will see the following content, indicating that the deployment is successful.

Note: The first address is the package source address, which is required when vs is configured. The second address is used to upload the package. For details about the tutorial, refer to other blogs. There are many methods. Pay attention to this, if you do not want to use APIKey, you can set it to false in the configuration file.

2. Configure the NuGet Reference Path in vs (tool --> Option --> NuGet package manager --> package source)

In this way, you can switch to your server after downloading the package.