Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgrading Applications

Status
Not open for further replies.

SirDrinksalot

Programmer
Feb 27, 2002
5
GB
Hi there all,

I'm looking to upgrade an application we've built using VB6, but i am encountering some problems which i hope you may be able to help me with. In the past, i would just build a new executable and include any new dll's, ocx's etc and copy these onto the PC(s) in question. Now however, i am faced with a massive re-write of the system, and an operations team who insist on deploying using SMS. We have also migrated from the P&D wizard to Visual Studio Installer (in order to be able to use SMS), but i have no idea how i am going to replace existing versions of the software. Essentially it involves:

a) Removing a dll (for connection to a database using OO4O)
b) Removing a run-time application (MapX) - 3rd party software
c) Installing the new MapX files (already got this bit sussed, but thought i'd include for completeness)
d) Installing Oracle Client via SMS (which i've been told can't be done, but that was by a DBA, who just doesn't want me to)
e) Installing new dlls & executable

Does anyone have any ideas how you can remove software / files as part of an installation?
Does anyone know if you can install Oracle Client via SMS? (off-topic i know, but thought i'd ask)

Anyway, hope someone can help me, cos no-one here can!!

Dan
 
Dan,

SMS provides scripts that can be used when deploying apps and each package deployed via SMS should have a related uninstall routine as part of the SMS coding.
The SMS team can test to see if your application is already present (you know where it goes and what it's called) and if so, then trigger the SMS Un-Install routine for the old package. (You will probably need two uninstal scripts - one for the old product not covered by SMS and one for the new one).
The Oracle client shouldn't be installed implicitly as part of your SMS package, however, again by using scripts, you can confirm that it is present on the client and if not then trigger the SMS Oracle Client package to install it.

SMS is a good tool for managing medium to large volume deployments and for allowing central control of software distribution. It does however require a lot of forethought and discipline in the application design and SMS package creation process. Your SMS team should know how to create SMS scripts with in-built logic and processing.
I'm not an expert in SMS, but in a previous role had to understand what it was capable of because the numpty's that were being used didn't understand it's capabilities!
Hope this helps.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top