Hi there,

While repackaging you always bump into dll's or exe who make use of Com registration. During the training i was told to put as much of that into the com registration tables in Adminstudio. Unfortunatly that table only supports Inprocserver and localserver as context of a com class. Just wandering how all u other repackagers handle com registration keys. Do you just leave it as is or u use other tactics? Im also looking for some more info on this com registration. How everything is related to each other for instance.

Thanks in advance

Dennis
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hi!

If you use Snapshot when you repackage an application, the COM-registration comes into the MSI-file and your component including the file has got the name ComponentName_COM, that means that

If you use Installation Monitoring, the COM-registration doesn't come with the package. You need to go to the component that contain the COM-registration and set "COM Extract at build" to "Yes". It will not include it in the package, but the MSI-engine will extract the registry when executing the package.

If you include a file to the MSI-package, you need to set the "COM Extract at build" to Yes. (...as far as I know....)

I hope this information will help you!

/Jonas
Answered 11/04/2005 by: jonasm
Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity