|
|
| Bill Angus 2005-12-01, 7:00 pm |
| I just created an installer using VS2005 according to the directions in the docs. On running the setup.exe generated by VS2005 -- the target machine (Win2000 pro) reports that it cannot install -- missing stdole on this machine.
I went back and checked/added MDAC to the pre-requisites listed in the project. Still no joy -- the install fails reporting stdole as missing. This is a VB app. Is there something else I need to include -- or should I uninstall MDAC and pror to retrying the install?
Any ideas greatly appreciated.
Have a great day!
Bill Angus
| |
| Bill Angus 2005-12-01, 7:00 pm |
| Oh yes.. I forgot to mention that when I added MDAC as a project dependency -- the next version of set did install MDAC on my test machine... then it said that it needed to restart the machine to continue setup -- so I restarted the machine, and the setup never restarted. Subsequently trying to run the setup.exe resulted in the setup terminating with the message that stdole needed to be installed on the machine and that setup could not continue.
I was installing the setup image from a subdirectory of the development machine via the windows network (I did not actually burn a CD).
| |
| Bill Angus 2005-12-01, 7:01 pm |
| Solved... in the publish properties I set an option to COPY the dependency STDOLE (instead of leaving the default which was NOT COPY for this dependency). It turns out there was a copy of STDOLE on the target machine -- but VS2005 sets a version requirement and it has to have exactly the right version of STDOLE to allow installation and use of the VB App.
|
|
|
|