It has been reported to me that an Uninstall program I provided also uninstalls or corrupts components needed to run vbs scripts. Could this be a Windows installer version conflict. I am installing components needed by VB6 runtime.
What appears to have happened, testing by the client will confirm, is VBSCRIPT.dll was installed in our application directory. The install routine registered VBSCRIPT.dll pointing to our application directory. Would have gone unknown, but, when the user uninstalled the application from training machines VBSCRIPT.dll was removed from the application directory leaving the registry still pointing to the just removed DLL. When other programs requiring VBSCRIPT.dll ran they failed as they could no longer find VBSCRIPT.dll.
The solution was easy, go to the c:\windows\system32 directory and register the operating systems VBSCRIPT.dll.
I know this a lesson for us to be more careful with the scripts, but is there a method in future versions of Advanced Installer which will not allow registering of operating system provided files.
I know this a lesson for us to be more careful with the scripts, but is there a method in future versions of Advanced Installer which will not allow registering of operating system provided files.
AI allows you to specify the COM modules to be registered at install time. However, the actual registration is performed by Windows Installer. Imposing a restriction in AI such that certain files cannot be marked to "auto register" based on their names would not be appropriate.
FOLLOW US
Get the latest news in Application Packaging