The method used here is to have all the master dlls in one location on the
server and have the menu application detect if a dll has changed. If so it
is copied to the local drive and run locally. This allows you to update the
master dll without having to rename it. The other thing to maybe consider is
having your menu application notify the user that there is a new version to
run and to restart the application. I only mention this because typically in
manufacturing environments applications rarely get turned off.
   

        -----Original Message-----
        From:   [EMAIL PROTECTED]
[SMTP:[EMAIL PROTECTED]]
        Sent:   Tuesday, 8 October 2002 14:02
        To:     Multiple recipients of list delphi
        Subject:        [DUG]:  What's an elegant way to migrate s/w
updates?

        We have about 70 users, running from a menu (exe), various apps
(dlls). If
        during the day, we have an urgent fix to an app, it's almost
impossible to
        get everyone out in order to update it. Is there a way to implement
some
        procedure where I can migrate a change to app xyz, with the name
xyz_ver2?
        When a user leaves app xyz and goes back in, they automatically end
up
        running app xyz_ver2. In this way the users painlessly move on to
the new
        version.

        Are there products out there for this? Could I code a simple
do-it-yourself
        version?

        My initial thoughts - in the menu program, when a selection is made,
e.g.
        Client Maintenance, I read a text file called
ClientMaintenanceVer.txt. In
        the text file is the current dll version to run e.g.
ClientMaintenanceV1_1.
        If I want users to move on to V1_2, then I prepare the dll, then
change the
        text file to point to the new dll. Sound o.k.? Any improvement on
that?

        Any ideas would be great.

        Thanks.

        Dave Jollie
        Software Developer BOA IT
        09 368 4259 ext 6231

        The information contained in this mail message is confidential and
may also
        be legally privileged. If you are not the intended recipient, please
note
        that any use, dissemination, further distribution, or reproduction
of this
        message in any form what so ever, is strictly prohibited.  If the
mail is in
        error, please notify me by return E-mail, delete your copy of the
message,
        and accept my apologies for any inconvenience caused.

        
---------------------------------------------------------------------------
            New Zealand Delphi Users group - Delphi List -
[EMAIL PROTECTED]
                          Website: http://www.delphi.org.nz
        To UnSub, send email to: [EMAIL PROTECTED] 
        with body of "unsubscribe delphi"
        Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/

DISCLAIMER:  This electronic message together with any attachments is 
confidential.  If you are not the intended recipient, do not copy, disclose or 
use the contents in any way.  Please also advise us by return e-mail that you 
have received the message and then please destroy.  Carter Holt Harvey is not 
responsible for any changes made to this message and / or any attachments after 
sending by Carter Holt Harvey.  We use virus scanning software but exclude all 
liability for viruses or anything similar in this email or any attachment.
---------------------------------------------------------------------------
    New Zealand Delphi Users group - Delphi List - [EMAIL PROTECTED]
                  Website: http://www.delphi.org.nz
To UnSub, send email to: [EMAIL PROTECTED] 
with body of "unsubscribe delphi"
Web Archive at: http://www.mail-archive.com/delphi%40delphi.org.nz/

Reply via email to