On 5/2/14, 9:31 AM, Peter Cushing wrote:
Paul McNett wrote:
So anyway, build the .exe and push it up to a server somewhere.
Configure the app to check for a later version and if it's there,
download it and copy it on top of the existing .exe, and restart. It's
one of the best things I ever did - hassle-free for the user as well
as the administrator and developer.
I'm just in the process of changing my app to have a loader EXE, then
depening on certain conditions it loads an APP file. This means I can
have certain users (or groups) running different versions of the program
and for updates (like above) you don't have to overwrite the EXE, so if
it all goes south you can make adjustments and put them back on the old
version. You also don't have to boot everyone out to put an upgrade on:
Copy the new APP in, change a setting and new users logging in get the
new one.
The loader.exe I made back in VFP6 worked so well I never upgraded it.
Oh, I also keep all VFP runtimes in my app directory, and I don't
register the DLLs. Why make simple things hard?
Paul
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message:
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
