If what you said about file versioning issues is correct then in the very first message in this thread I would have expected the second install NOT to install the component if the version was the same... and more importantly not to uninstall it. This is not what is ...
I think there is still an issue lurking here though...
What if a newer version of "thirdparty.ocx" exists on the target PC before "mypackage.msi" attempts to install it? Surely there must be some way of preventing the older one being installed?
Thanks Cata That will work fine for components I own and written by me.
However, the installation package might also include third-party files (mostly Microsoft) say something like comdlg32.ocx or mscomctl32.ocx that reside in the winsysdir.
Other applications (not written by me) may use either ...
I have come across an unexpected behaviour on application uninstall.
A client installs more than one application I developed (say 2) and both use a series of custom components that are designed to be shared. When the second app is uninstalled it removes custom components installed by the first app ...
Finally got round to modifying my "brute force" install as per your suggestions. It does not seem to be working as you indicated though.
Install set up to create... HKLM\SOFTWARE\myco\myapp\name1=value1 HKLM\SOFTWARE\myco\myapp\name2=value2 etc. I then use ORCA to Add the LockPermissions table and ...
1.) The "everyone" question really meant - Is the group "everyone" always present in the security system? Specifically would older NT systems know about it? Or maybe this doesn't matter as long as the key gets the GENERIC_ALL permission?
I note the earlier message from Steve (Mar 23) about this.
OK, changing permissions will be in a later release? When? I have an app I need to deploy now that needs to make entries at run-time. Currently I have these set up in HKLM\Software\myco\myapp but they could be anywhere.
OK thanks. I am not a "C" programmer so my only option would be to build the .exe in VB6 - no problem. However will I run into bootstrap problems doing this? i.e. at the FIRST install are the VB support files (e.g msvbvm60.dll etc) I include in my package, installed and registered by the time the ...
After some experimentation I found that I could get the [TARGETDIR], in my case to store a registry key, by adding an entry in the registry section thus...
HKLM\SOFTWARE\MYCO\MYAPP
with a Name: myname
and a Value: "[TARGETDIR]"
Hope this helps
Pete
Yes but HOW do I do that?
I need to check for the registry key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess
and check the value of FullInstallVer (i.e. FullInstallVer >= "2.50.000")
Can this be done inside AvancedInstaller or do I have create an external file?
FOLLOW US