com

If I have a C++ class, X, which implements the COM interfaces IY and IZ, and I have a pointer y to the IY interface of an object of type X, and I do this: IZ *z = dynamic_cast<IZ *> ( y ); That doesn't bump the object's reference count, does it? I don't have to do a Release() to account for it, right? If it matters, I'm using ATL/COM. I'm guessing the answer is "no it doesn't bump the reference count, and no you don't have to Release()", but I want to make sure. Thanks in advance. Reference counts for COM objects are incremented when someone calls IUnknown::AddRef(). QueryInterface(),

Using .NET 4.0, I have made a COM-enabled DLL (let's call it example.dll), and I have registered it and generated the respective type library using regasm.exe (regasm.exe /tlb /codebase example.dll); the type library is called example.tlb. The assembly is strongly named. This works so far, and I can use the DLL and the TLB from within VBA. But for certain reasons, I need to make my own utility which does the DLL registration and TLB generation. Basically, this utility will be in the same directory as the DLL and should register the DLL which it finds in that directory as well as generate the

When I don't configure a client DLL ( globalsd.dll ) to use Isolated COM to access a .NET assembly that exposes a COM interface ( FSCulture.dll ) before running the main executable ( FCMTSYSM.EXE ) I get an application exception (Access Violation) as the CoCreateInstance fails during the static initialization of the DLL ( syslev0.dll ) that calls the client DLL ( globalsd.dll ) during startup (the code continues to try to run and use the non-existent COM object). This much I understand and can deal with. I need to improve the error handling and/or register the COM object with regasm and/or