Re: Experiences with App Updater

Stacey Levine <[email protected]>
Newsgroups gmane.comp.windows.devel.dotnet.winforms
Message-ID <A48E95FB3D4D02449554AE952F3B3E4702FC4411@vmcexchng.www.musicforasong.net>
I use the manifest method. So when I am ready for a  release, I put the
files on the server and then change the manifest file.  The application
checks every 15 minutes (that is how I have it set - you can change
that) for updates. When it finds a new version, it donwloads the updates
and then presents a screen to the user that a new version is available
and asking if they want to use it.  If they say no, that is fine - the
next time the application starts up, it uses the new version any way.

Now.. some of my updates do require that they update. What I do in this
instance is put the release out at night. My application creates a
scheduled task that opens itself up at 1AM just for these instances.
This way it makes sure that it does get the updates. The application
also closes itself at 6AM to get rid of the Update available message.

-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:[email protected]] On Behalf Of
Greg Robinson
Sent: Monday, April 09, 2007 9:21 AM
To: [email protected]
Subject: Re: [DOTNET-WINFORMS] Experiences with App Updater

Do you allow your users to decide when to do the update? Or do you just
push
the update as soon as the server files have been updated?

One thing on our mind is sprocs.  If Release XX required an update to
sproc
"insert this" when do we update the sproc?  Right before the server
update?
There is a chance a user running the 'older' version could hit the wrong
version of a sproc.




Greg Robinson
Custom Data Systems, Inc.
www.cds-am.net

-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:[email protected]]On Behalf Of
Stacey Levine
Sent: Monday, April 09, 2007 9:16 AM
To: [email protected]
Subject: Re: [DOTNET-WINFORMS] Experiences with App Updater


We use it here to keep multiple applications up to date. The biggest
deployment is 200+ computers to more than 50 remote locations.  I have
had only a few problems. The biggest is if someone has the application
open and it is updating the files and then they close the application.
At least I think that is the problem.  Every now and then the result is
that a computer gets half-updated and then the application doesn't
start. It is easy to fix by pointing the appstart.config back to the old
version directory and opening it back up.

-----Original Message-----
From: Discussion forum for developers using Windows Forms to build apps
and controls [mailto:[email protected]] On Behalf Of
Greg Robinson
Sent: Monday, April 09, 2007 7:24 AM
To: [email protected]
Subject: [DOTNET-WINFORMS] Experiences with App Updater

Are app is currently no touched deployed from a web server.

We are considering using the App Updater.  Can those who have used it,
or
are using it, report their experiences with it, the good, the bad and
the
ugly?

Thanks,




Greg Robinson
Custom Data Systems, Inc.
www.cds-am.net
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.