EDN Admin
Well-known member
<div style="margin:8px
Hi,
I have an activation context problem and SxS issue. Hopefully Ill be able to explain it well.
I have COM library containing many COM classes and interfaces - this library is shared between several applications.
I have an application using this COM library.
Till now, the COM library was registered on the machine, so my application was able to use it.
From now on I want my COM library to be deployed on the machine with no registration.
In order to make it work, I created a manifest file for my COM library and I wanted to use the activation context API in order to enjoy SxS and registration free capabilities.
I thought that if lll add to my application creation/activation of Activation Context in the beginning of application and will deactivate/release the activation context during the application termination process all will be fine.
I was wrong :-(
My application opens and closes various forms and dialogs, not all of them were developed by me. This somehow affects the activation contexts stack and my CMO library cant be used.
Note that if Ill reduce the scope of the activation context creation/destruction to wrap each and every COM library call , the problem will be solved.
This solution is not acceptable since my application is already on the market and wrapping each and every COM library call is no acceptable.
Is this problem familiar? if so, is there a way to overcome it?
Is there a way to define activation context per the entire process and not per thread?
Thanks,
R.
View the full article
Hi,
I have an activation context problem and SxS issue. Hopefully Ill be able to explain it well.
I have COM library containing many COM classes and interfaces - this library is shared between several applications.
I have an application using this COM library.
Till now, the COM library was registered on the machine, so my application was able to use it.
From now on I want my COM library to be deployed on the machine with no registration.
In order to make it work, I created a manifest file for my COM library and I wanted to use the activation context API in order to enjoy SxS and registration free capabilities.
I thought that if lll add to my application creation/activation of Activation Context in the beginning of application and will deactivate/release the activation context during the application termination process all will be fine.
I was wrong :-(
My application opens and closes various forms and dialogs, not all of them were developed by me. This somehow affects the activation contexts stack and my CMO library cant be used.
Note that if Ill reduce the scope of the activation context creation/destruction to wrap each and every COM library call , the problem will be solved.
This solution is not acceptable since my application is already on the market and wrapping each and every COM library call is no acceptable.
Is this problem familiar? if so, is there a way to overcome it?
Is there a way to define activation context per the entire process and not per thread?
Thanks,
R.
View the full article