G
Guest
Hi
I just made an installer for an application that uses two external COM dlls.
On the surface, everything seems to be running smoothly and the the
application runs without any errors. However, I am not completely satisfied
by my implementation.
I basically used a software that generates an msi file quite easily and
included the two dlls in my package. I then edited the msi file using orca,
and forced the dlls to self register by stating their FileName key in the
column of the SelfReg table. Nothing wrong there...
Now here is my concern:
The SelfReg table makes a unique registry entry in the HKCR logical section,
by overwriting the already existing key. That's still acceptable but the
problem is that on uninstalling the application, the installer also
unregisters these two dlls, which is undesirable as they might be needed by
other applications which now must register the dlls again.
Ideally, shouldn't the installer make a new key in the HKCU section, which
does not effect the previously existing registry entry? I don't know how it
could be done but if somehow the installer could generate a separate key for
the copy of dlls being used by my application, then on unregistering them,
the other applications wouldn't get affected (or so I'm guessing).
I would appreciate if anybody could suggest a better way to do this.
Thanks!
I just made an installer for an application that uses two external COM dlls.
On the surface, everything seems to be running smoothly and the the
application runs without any errors. However, I am not completely satisfied
by my implementation.
I basically used a software that generates an msi file quite easily and
included the two dlls in my package. I then edited the msi file using orca,
and forced the dlls to self register by stating their FileName key in the
column of the SelfReg table. Nothing wrong there...
Now here is my concern:
The SelfReg table makes a unique registry entry in the HKCR logical section,
by overwriting the already existing key. That's still acceptable but the
problem is that on uninstalling the application, the installer also
unregisters these two dlls, which is undesirable as they might be needed by
other applications which now must register the dlls again.
Ideally, shouldn't the installer make a new key in the HKCU section, which
does not effect the previously existing registry entry? I don't know how it
could be done but if somehow the installer could generate a separate key for
the copy of dlls being used by my application, then on unregistering them,
the other applications wouldn't get affected (or so I'm guessing).
I would appreciate if anybody could suggest a better way to do this.
Thanks!