What is the advantage of putting com registration in advertising tables.
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
Answers (4)
Please log in to answer
Posted by:
AngelD
15 years ago
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.
Posted by:
turbokitty
15 years ago
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.
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.
Posted by:
anonymous_9363
15 years ago
Posted by:
turbokitty
15 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.