Unpublishing a ClickOnce Application.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We are having good results with ClickOnce deployment of a Winforms application
on our intranet, using VS2005. However, we mistakenly published a new
experimental build. How can we "unpublish" it?

Can someone tell me what the correct procedure is? Is this documented
somewhere? Would the following procedure work to unpublish version 1_0_0_74
of application "XXXXX:"

1. In the deployment folder on the server, delete the file
"XXXXX.application."

2. Rename the file "XXXXX_1_0_0_73.application" to XXXXX.application."

3. Delete the folder "XXXXX_1_0_0_74" and the file
"XXXXX_1_0_0_74.application."
 
Can someone tell me what the correct procedure is? Is this documented
somewhere? Would the following procedure work to unpublish version
1_0_0_74 of application "XXXXX:"

1. In the deployment folder on the server, delete the file
"XXXXX.application."

2. Rename the file "XXXXX_1_0_0_73.application" to
XXXXX.application."

3. Delete the folder "XXXXX_1_0_0_74" and the file
"XXXXX_1_0_0_74.application."

Should work, just make sure, that the 1_0_0_73 application folder is
still available...
Otherwise, make a 1_0_0_75 build (that is exactly the same as the 73
build, just with another version number), and publish this to the server.

hth
Markus
 
Making a 1_0_0_75 build (that is exactly the same as the 73
build, just with another version number), and publishing this to the server,
should be easy if we "label" the source files in our document repository when
we published. If not, it would be an error-prone process.
 
Making a 1_0_0_75 build (that is exactly the same as the 73 build,
just with another version number), and publishing this to the server,
should be easy if we "label" the source files in our document
repository when we published. If not, it would be an error-prone
process.

You are using a source control?
If yes, it should be possible to go back to a certain date, no matter if
you label them or not (at least this is the way, how it works with
subversion or cvs).

Markus
 
Back
Top