-
The application I'm working on provides self-upgrade functionality, which replaces the current application when a new version is released (via ftp process).
I don't have problem replacing the existing application (.exe file). However, sometimes addinging or updating .dll and .ocx files with the new version is required, and thus might need to know where the file is installed (because it's not under the program directory) and do something to the window's registry.
In the past, when adding or updating these files is required, a new set of setup disks is distributed, uninstall old version followed by installing a new version and let setup wizard do the job. This is an inefficient and tedious process.
I'm looking for a way similar which automatically replaces the required files in the required directory -- similar to installing service packs. How to find out where the originally file is and update the registry with the new version?
Any suggestions on how can this be done, preferably without using 3rd party software?
-
Are the DLLs and OCXs your own and specifically for your exe ?
or are they standard VB components?
If they are your own than that's not a problem because you can control where they are, but manually upgrading VB components might cause compatabily problems with other software using them if versions etc aren't checked as well.
-
They are 3rd party files which is upgraded from time to time, or VB componets, like when I included a new standard VB controls that didn't exists in the previous version.
-
These should be in the c:\windows\system folder if your app install is typical and evil. If not, the registry lists the file location somewhere. Still no luck? Load the sample Setup projects with VB and they will show how to find the windows folder name from APIs (if its something like f:\microsoftsbeautifullymessedupos\system\ instead of c:\windows\system, for example)
