If you use Shared members in .NET or modules in VB6, you reduce COM+ context overhead without any risk whatsoever that you will get extra context overhead for that code. You also release yourself from the clean-up burden that you have in both worlds. Instead of the VB6 consumer code:
Even though you may want to use some COM+ services, it doesn’t mean that you have to have a unique context for each and every instance. The root instance, that is, the instance that the client uses, must have a context, but the secondary instances can often co-locate within the
Instances of configured components, that is, components configured in COM+, get runtime services owing to context objects. When you instantiate a COM+ component, your instance will live in a context object. When you call a method of your instance, the call will go through the context and that is when
In another item in this Tip Bank (see link below), we mention that you can co-locate secondary instances within the context of the caller. If you don’t need any services at all for your secondary components, then you don’t have to configure them as COM+ components either. You lose the