-
Hi all
This is somewhat of a constant equation of trouble for me when deploying scripts or and working on setup applications.
Using Package & deployment Wizard: (I am only interesting with PDW no third pary software is to be considered)
I have already deployed my applications to 20 end users clients.
This application uses an ActiveX control (ocx). Both package and deployment scripts still exist.
After sometime later I acquired a newer version of this OCX control which is better in perfomance + other benefits.
Now my 20 clients want to make use of this OCX. What would be easiest and quicker way to transfer this ocx to them?
Please be a little descriptive as i am not a full developer and as i am already confused by going into in-depth reading on Package and deployment wizard!
-
Hi
You probably do not want to go and repackage your application and redistribute it, so you won't be able to use the PDW.
In this situation, i would create a batch file (or VBScript file) and include the OCX and Regsvr32.exe. Have the end user run the batch file which will update the OCX (copy it to the App Dir or System Dir) and register it using Regsvr32.
Make sure the OCX is version compatible with your previous OCX so your clients will continue to function
Tom
-
Thanks Clunietp
What other alternatives do I have similar to this one? And if I was to use the batch file then would I have to unregister the earlier OCX first before registering the newer version?
Many thanks
-
Alternatives to PDW or a batch file? I'm not sure of anything else that's as easy....
you should not have to unregister the old component as long as your new OCX has binary compatibility with your previous version
