Hi All I'm developing COM+ components in VB.NET and have a fair bit of experience with COM+. I cannot solve the following however: Each one of my components activates in their own context. As far as I understand, this has a fair bit of overhead, and want to get them to activate in the same context as far as possible.
Nearly all objects are declared as follows: <Transaction(TransactionOption.Required)> _ Public Class clsClient ..... I do not set any other attributes, as I do not use role based security etc. Wheter I run it as library or server package does not make a difference. The property I examine to check wheter they run in the same context is : ContextUtil.ContextId Now, as far as I understand, COM+ checks wheter they can live in the same context, and if so, it creates them in the same context. However, my objects do not active in the same context, even if I try and force it using the Must active in callers context, which return an activation error. When I make the child components non configured, they then activate in the callers context, which gives a huge speed improvement, and this is what I am looking for. Any ideas as to what properties might influence why it is created in seperate contexts? Thanks JC Oberholzer =================================== This list is hosted by DevelopMentor� http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
