03-27-2013, 04:52 AM
Yes.
If you use manifest like __ComActivator ca.Activate("PACSWebServiceWrapper.X.manifest"), don't need to add the manifest to the dll.
If you don't want to distribute the manifest file, then you can add the manifest to the dll, and __ComActivator ca.Activate("PACSWebServiceWrapper.dll,2")
If Activate speed is important, use flag 1.
The ComActivator variable must be still alive when the macro uses _create. If need, use thread variable, not local. Never use global variables.
If your macro need to _create objects of classes from several dlls, create manifests for each dll. Then:
__ComActivator ca1.Activate("PACSWebServiceWrapper1.X.manifest")
Typelib1.Class1 x1._create
__ComActivator ca2.Activate("PACSWebServiceWrapper2.X.manifest")
Typelib2.Class2 x2._create
If you use manifest like __ComActivator ca.Activate("PACSWebServiceWrapper.X.manifest"), don't need to add the manifest to the dll.
If you don't want to distribute the manifest file, then you can add the manifest to the dll, and __ComActivator ca.Activate("PACSWebServiceWrapper.dll,2")
If Activate speed is important, use flag 1.
The ComActivator variable must be still alive when the macro uses _create. If need, use thread variable, not local. Never use global variables.
If your macro need to _create objects of classes from several dlls, create manifests for each dll. Then:
__ComActivator ca1.Activate("PACSWebServiceWrapper1.X.manifest")
Typelib1.Class1 x1._create
__ComActivator ca2.Activate("PACSWebServiceWrapper2.X.manifest")
Typelib2.Class2 x2._create