com-interop

I get the following exception when trying to load an ASP.NET MVC website: Unhandled exception at 0x07070a91 in w3wp.exe: 0xC0000005: Access violation reading location 0x00000000. The Visual Studio Just-In-Time Debugger opens and the only information I can see in the debugger is this: Call stack location: msvbvm60.dll!06c00a91() The website uses some COM objects and everything worked fine until last week. This problem appeared out of the blue. This is the error log from Windows Event Viewer: Faulting application name: w3wp.exe, version: 7.5.7601.17514, time stamp: 0x4ce7a5f8 Faulting module

As I get it there're three ways to implement marshalling in COM: typelib marshalling proxy/stub marshalling implementing IMarshal by the object now how does the component consumer (user) choose which one will be used? Does it decide on its own and use the preferred way or does it call some built-in function and it solves the problem for it? I currently experience the following: my component implements a custom interface ICustomInterface that is also implemented by a component from another company. My component doesn't have a typelib and doesn't implement IMarshal. The system registry contains

I have a single-threaded application that uses COM objects. At the beginning I in effect call CoInitialize(0) twice - once in my code and the second time in the code of another subsystem of the application. The first call returns S_OK , the second returns S_FALSE - exactly as MSDN says. When the application stops it calls CoUninitialize() twice but between those calls it tries to call methods of some COM objects - those calls just crash with access violation because I suppose the COM objects are finalized and released at the first call to CoUnitialize() . If I remove the duplicating calls to

I am new to COM and have to create a COM wrapper for a C++ dll, to make some functionality in it accessible for managed code. I mainly followed this tutorial on code project to create a COM ATL dll. I created a post-build-step that calls tlbimp.exe on the COM dll to create the wrapping. Adding a reference to the dll that tlbimp.exe creates works, and I get code completion for methods on my COM dll, and can compile managed code that uses that dll. However, running that code leads to the following exception: Unhandled Exception: System.Runtime.InteropServices.COMException: Retrieving the COM