|
Avoid duplicate entries for the same serviced component
|
Total Hit (2693) |
A common mistake when creating a .NET component that runs under Component Services - that is, a class that inherits from ServicedComponents - is that you forget to assign a fixed version and/or GUID to the component being built. In this case, whenever the assembly is modified and recompiled, a new v
....Read More |
Rating
|
|
|
Reduce COM+ context overhead: activate in the caller's context
|
Total Hit (2774) |
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 first context.
In
....Read More |
Rating
|
|
|
Reduce COM+ context overhead: use modules and shared members
|
Total Hit (2786) |
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:
«Code LangId
....Read More |
Rating
|
|
|
|
Support COM+ constructor strings in serviced components
|
Total Hit (2877) |
Having a VB6 component support a COM+ construction string requires that you implement the IObjectConstruct interface and its only method, Construct. The .NET ServicedComponent class implements this interface internally and expose the Construct method as a protected, overridable method. Thus your VB.
....Read More |
Rating
|
|
|
Take advantage of COM+ object pooling
|
Total Hit (2742) |
VB6 objects can't be pooled under COM+, because they are apartment threaded. This restriction is void with VB.NET objects (and all .NET objects in general), because they are free-threaded. To make an object poolable you just need to decorate the class with the ObjectPooling attribute:
«Code LangI
....Read More |
Rating
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Component Services for .NET, Part I of IV
|
Total Hit (2275) |
The topic of component services is about creating enterprise applications that need to be secure, reliable, available, efficient and scalable. Component Services, aka COM+ (previously MTS), is the part of the Windows Server OS that supports these goals. The idea is that integrating your application
....Read More |
Rating
|
|