Using nuget to manage and update the class libraries shared within the team is a good method, and it is integrated with CI tools. During the build process, nuget is packaged and distributed to public projects. The nuget private server construction method is as follows:
1. Open the Extension Manager window in vs2010 and select nuget Package Manager for download:
2. Install nuget Package Manager:
3. Restart vs2010
4. Use vs2010 to create an empty web application project:
5. Open manage nuget packages
6. Search for nuget. server and install:
7. Select the new web application project and apply the nuget. server package to it:
8. Open the web application project and check that nuget. server and related dependencies have been added to the reference. This is the convenience of nuget :)
9. open the web of the Web application project. config, add a guid to apikey. As described in the config file comment, this GUID is the password used when the push and delete nuget packets are sent to our private server:
10. Publish: the Web application is sent to IIS, and the server is created :)
11. Test the website:
12. If everything is normal, you will see the following page:
13. As shown on the page above, visit http: // hostname/nuget/packages to view the nuget package on the current server:
14. Now, we can use nuget.exe to push our nuget packets to our nuget server.
15. then configure the client vs2010 (which is required by every developer in the team), open option, and find Package Manager-> package source, add the address of our nuget server to it:
16. Now, open our manage nuget packages and you will see the newly added internalnuget: