.net (winforms, not asp) multi-server deployment

Question

I have a small .NET WinForms application and a couple of Linux servers, DEV and CL1, CL2..CLN (DEV is the development server, and CL * are the servers that belong to our clients, they are in private networks, and this is a type of production server )

I need an update mechanism, so (1) I develop a new version and publish it in DEV
(2) DEV server users install the latest version from DEV
(3) CL2 users (client2 employees) install the stable version from CL-2 directly
(4 ) checking applications for updates using the server on which it was installed (therefore, if it was installed with CL-2, it should check CL-2 for updates)
(5) I should be able to distribute the update to the selected CL server (using only a copy of the file and possibly sed, not perei building) if I want it (and if I don't, this CL server will have the old one until I manually update it)

I tried using clickonce, but it looks like it meets only the first two requirements.

What should I do?

Answer 1

ClickOnce needs to handle 1-4 to be honest. All that is required is that for each site that you want to deploy / update, you will need its own publication, which after viewing your specifications is not incorrect.

What could you do to make 5. applicable, create an automated process for republishing the file. This can publish and then upload to the correct server.

Remember that ClickOnce needs a new manifest for each version, and publication requires a new manifest, so I'm not sure if you get around 5. with a simple file replacement.

Answer 2

. 5- , , URL- , .

Answer 3

, DEV, QA, PROD. , , , cmd , MSBUILD. URL- . DEV QA AssemblyName , 3 . , , .

, , . http://msdn2.microsoft.com/en-us/library/ms165431(VS.80).aspx

@Kyle, For the above solution, different versions may work side by side or you get errors indicating that the application is already installed.