v.7.20 unregister components after Process
Posted: Tue Nov 04, 2014 9:05 pm
First of all, I tell you that with the previous version 7.10 I have never had any problems and I'm successfully deploying my VS6 installer v.4.0 (http://nuke.vbcorner.net)
Using the latest version 7.20 happened to me a disaster.
I wanted to try with my application in which I use some OCX provided with VB6 (Windows Common Controls 6, etc.) And other third-party DLL and OCX (ComponentOne, DataDynamics, etc.).
So I simply added all the OCX / DLL under %DEFAULT_FOLDER% and set for each component the flag Register as ActiveX (COM) component without touching any other options, then run Process.
After this I have run the myapp_boxed.exe to try if this is start.
Today I restarted the same VBP project that I was studded with errors pointing that all components were no longer registered!
Because all resume his work, I had to 'repair' install VB6.0 EE and all suite components (ComponentOne, DataDynamics, etc.).
Frankly, I was thrilled!
What might be the situation?
Thank.
My system is:
Visual Basic 6.0 Enterprise Edition - SP6
Windows 7 64bit - SP1
Using the latest version 7.20 happened to me a disaster.
I wanted to try with my application in which I use some OCX provided with VB6 (Windows Common Controls 6, etc.) And other third-party DLL and OCX (ComponentOne, DataDynamics, etc.).
So I simply added all the OCX / DLL under %DEFAULT_FOLDER% and set for each component the flag Register as ActiveX (COM) component without touching any other options, then run Process.
After this I have run the myapp_boxed.exe to try if this is start.
Today I restarted the same VBP project that I was studded with errors pointing that all components were no longer registered!
Because all resume his work, I had to 'repair' install VB6.0 EE and all suite components (ComponentOne, DataDynamics, etc.).
Frankly, I was thrilled!
What might be the situation?
Thank.
My system is:
Visual Basic 6.0 Enterprise Edition - SP6
Windows 7 64bit - SP1