COM+ Application - Where is it stored?
Hi all,
I need to change some settings in a COM+ Application located in Component Services which is installed with my app (Vendor msi).
I have tried using both InstallRite and InstallMaster to capture any changes I make to the COM+ application in question, however it doesn't really give much away.
I notice that a couple of files in C:\Windows\Registration get modified but not exactly everything I need.
Where is the information for COM+ Applications stored so I can modify a COM+ Application through my package?
Thanks.
I need to change some settings in a COM+ Application located in Component Services which is installed with my app (Vendor msi).
I have tried using both InstallRite and InstallMaster to capture any changes I make to the COM+ application in question, however it doesn't really give much away.
I notice that a couple of files in C:\Windows\Registration get modified but not exactly everything I need.
Where is the information for COM+ Applications stored so I can modify a COM+ Application through my package?
Thanks.
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Jack_Mcall
18 years ago
You dont half come up with tough ones mark.
Life up north must be getting to you :(
Could you detail what you are trying to modify in the COM+ Application
Most of the COM+ info is registered the same as COM, Modifiying its data may cause its functionality to fail
About the only thing that could be modified is the location of the registered component dll , ocx etc
for this I would recommend that you use the WiseComCapture.exe to extract the com info from the component once you have it placed in its new location.. .
dont know if im way off the mark but its worth a try
Life up north must be getting to you :(
Could you detail what you are trying to modify in the COM+ Application
Most of the COM+ info is registered the same as COM, Modifiying its data may cause its functionality to fail
About the only thing that could be modified is the location of the registered component dll , ocx etc
for this I would recommend that you use the WiseComCapture.exe to extract the com info from the component once you have it placed in its new location.. .
dont know if im way off the mark but its worth a try
Posted by:
mark_holland21
18 years ago
Hey Jack_McCall if that is your real name,
thanks for that.
I eventually discovered that within the Vendor msi that I was provided, there was a Property called REMOTESERVERNAME and this had the original value that i was trying to replace in the COM+ Application.
I edited this value and found that the REMOTESERVERNAME had been used in the AppID table. This I guess is how this Vendor managed to populate the COM+ application values.
Thanks.
thanks for that.
I eventually discovered that within the Vendor msi that I was provided, there was a Property called REMOTESERVERNAME and this had the original value that i was trying to replace in the COM+ Application.
I edited this value and found that the REMOTESERVERNAME had been used in the AppID table. This I guess is how this Vendor managed to populate the COM+ application values.
Thanks.
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.