If we sort com registration keys (in the registry table) in with their respective dll's and ocx's in seperate components, is the repair functionality not equally good as when you put the com registration in advertising tables.
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
Interesting question.

Are you advertising any features in your MSI or are you an application vendor?
If you are, then this blog entry suggests you don't advertise the COM info.
http://robmensching.com/blog/posts/2007/3/12/RobMens-Recommendation-Do-not-advertise-COM-information-in-MSI

If you aren't advertising certain features and are repackaging, then I'd suggest advertising this info.

If you're using WISE, the setting is: "Scan advertising information into advertising table"

But that's just my opinion.
Answered 01/27/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
0
But that's just my opinion....and one with which I'm sure most of us here would concur.
Answered 01/28/2009 by: VBScab
Red Belt

Please log in to comment
0
Well that's good to hear. I thought I'd be flamed for that one. [:D]
Answered 01/28/2009 by: turbokitty
Sixth Degree Black Belt

Please log in to comment
1
If the question was "What is the advantage of putting com registration in advertising tables." I guess the answer would be "you get extra entrypoints to be able to trigger a self-check". Like TK mentioned; if you don't have any entrypoints ex. advertised shortcuts, then using COM-advertising would be the only way to trigger a repair if needed.
Answered 01/28/2009 by: AngelD
Red Belt

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