Reduce COM+ context overhead: use non configured classes
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
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
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
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
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.