We are developing a .NET 3.5 application (Windows Forms), which is comprised of 3 main parts.
As part of the deployment process, we’d like to be able to continuously update the components after being installed.
I have been thinking about setting up a NuGet server, and packaging component updates as NuGet packages.
Has anyone done such a thing before? Do you think NuGet fits this job?
Our requirements are:
- Receiving of packaged DLL files (but there may be scenarios of additional files in a package
- Detecting dependency on other components (or component versions)
- Auto detecting new component versions
We are using TeamCity for continuous integration and for building our product, i know it integrates well with NuGet and can directly create/publish NuGet packages.
The question is how well can i integrate NuGet with our application? is there any client NuGet code to consume packages? I am wondering if this can work out.
1 and 3) Deploying and receiving data from NuGet using NuGet.Core is possible. Check NuGet push… to Windows Azure and the source code for NuGet.exe’s Update -Self command.
We’re also featuring this scenario in our upcoming NuGet book – Pro NuGet.
2) Hosting your own feed is easy, check http://www.myget.org or use the NuGet gallery