Software Deployment

For the majority of the time, Merge Modules are the best way to go because they keep the Component GUID the same.

The absolute best method is to isolate the ActiveX component with your application. There are a few different methods for isolating files and its best to read up on the Windows Installer SDK.

ORIGINAL: mmmyllym

Problem is like this: mscomctl.ocx is an activeX component which is used by Microsoft Office and it's also referenced by Visual FoxPro 6.0 and Visual Basic 6.0
applications. It controls:

Microsoft TabStrip Control (v6.0)
Microsoft Toolbar Control (v6.0)
Microsoft StatusBar Control (v6.0)
Microsoft ProgressBar Control (v6.0)
Microsoft TreeView Control (v6.0)
Microsoft ListView Control (v6.0)
Microsoft ImageList Control (v6.0)
Microsoft Slider Control (v6.0)
Microsoft ImageComboBox Control (v6.0)

I need to deploy this component as part of the application. When I install Word and then my own appliction it will replace mscomctl.ocx. My guess is that this will break the check sum in Word and cause it to start self healing function when either one of the applications are started from the shortcut.

Is there any way to prevent this? I was thinking of utilizing mscomctl.msm merge module found here:

http://www.zerog.com/downloads_02d.shtml





What check sum?

I assuming mmmyllym means it breaks a component keypath of the Office installation, and hence why Office attempts to repair itself.

As far as I know all the short cuts that are created from MSI-packages include a check sum that is calculated when the application is started from this short cut.
MSI-packages have this self healing function that is based on this check. Check sum is calculated from file path, file name, version and such things. It will change if the one of the components is missing or have been replaced by another installation package. If the check sum doesn't match to the sum calcuted on compilation time it will try to reinstall application from network (=installpath).

If the file was replaced by a newer version, that means it is still there.

Therefore, the component isn't broken. So that can't be what he meant?

Thanks mmmyllym!

I've never heard about this, but I'd love to know more about it! I don't suppose you could tell me where to find documentation about this?

Thanks again.

It is mentioned in Windows Installer Technology for System Administrators, page 52

http://www.installsite.org/pages/en/msi/books.htm


The checking is based on keypath like brenthunter2005 mentioned. I think I have to read the chapter again. I remembered this thing incorrectly.

Thank you for your help.

[:D] LOL [:D]



PS: sorry.

I don't get the joke or the apology Brent? Presumeably you're saying that you still believe in some undocumented checksum that nobody can explain? I must say that I'm surprised if this is the case.

So I don't have to cover the same ground again, check the following topic:

http://itninja.com/question/faulttree-10546&mpage=1&key=ᚍ

If anyone can find any credible information anywhere that suggests that Windows Installer checks anything more than the "existence" of the keypaths within the feature when a shortcut (or other entry point) is invoked, please post it here so that it can serve as a reference for subsequent visitors. Maybe Microsoft could also include it in the SDK documentation too.

Please don't refer us to a page of a book that most of us don't have - this is of little value to anyone (unless you also quote relevant passages).

Just for clarification, I'm not talking about what is checked once a repair is underway - only what is checked every time you run an advertised shortcut.

@WiseUser - [;)] I was LOL about this 'checksum' stuff. I think mmmyllym has 'checksum' mixed up with component key path checks upon clicking on an advertised entry point.

[8D]

I'm sorry I doubted you Brent![;)]

This is getting to be a bit of a touchy subject - people keep suggesting that the component checking mechanism works differently to the way I thought it did. So, I start doubting my own understanding of the way it works!

I don't like being wrong, but if I am I still need to find out![:D]