Application Updates

  • Thread starter Thread starter Looch
  • Start date Start date
L

Looch

Hi All,

Forgive my lack of using the right terms here but I'm hoping someone
has an answer. I'm using VS 2005 C# Express and doing the following:
Right clicking the solution name and choosing properties, going under
the Publish tab on the left and clicking the 'Publish Wizard' button.
This launches the publish wizard and I am able to step through
resulting in my application being built and installable (I get four
files - a directory, two application manifests and the set up exe).
I'm not sure if this is a ClickOnce app, thus the confusion.

I want the application top check for updates and set the appropriate
file path in the wizard. Using the above mentioned process, what files
do I need to include in the directory that the update function looks
to? The updated source code files or an updated "built" version like
the one mentioned above?

Thanks in advance.
 
Using ClickOnce deployment, you simply set the Updates property in the
Publish tab to check for updates for running.

You deploy the application, the user installs it.

You deploy it again later after making some changes to the same location.

When the user runs the application, it checks the version, sees there is a
new one, and asks the user if he wants to upgrade. When he says Yes, it
pulls the files that have changed, and upgrades.

If you are not setting the minimum version, the user can do Add/Remove
Programs on your app, and it will ask him if he wants to completely remove
it, or just go back one version.

If you set the minimum version equal to the version you are deploying, it
will not ask the user if he wants to accept the update, it will just update
it. And he will only be able to remove it, not revert one version.

RobinS.
GoldMail, Inc.
 
Ah, so the deploy directory and the update directory could be the same
directory - I think that's where I was getting confused.

Thanks
 
They don't have to be. If you look in the Updates... screen under the
Publish tab on the project properties, you CAN set a different location. We
don't do that; we just publish to the same URL. That way, new users also get
the latest version.

I think the primary purpose of that is if you are going to deploy on a CD or
from a network location, and want the updates picked up somewhere else, like
from a web server.

RobinS.
 
Back
Top