com-interop

All of these questions: Excel 2007 Hangs When Closing via .NET How to properly clean up Excel interop objects in C# How to properly clean up interop objects in C# struggle with the problem that C# does not release the Excel COM objects properly after using them. There are mainly two directions of working around this issue: Kill the Excel process when Excel is not used anymore. Take care to explicitly assign each COM object used to a variable first and to guarantee that eventually, Marshal.ReleaseComObject is executed on each. Some have stated that 2 is too tedious and there is always some

A colleague of mine created an assembly in VB.net for use with JScript via COM interop. The assembly used to work fine, but we signed it and now it only seems to work on Windows 7 machines. I've tested 2 Windows 7 machines and 2 Windows Vista machines. When we signed the assembly and we try to instantiate the ActiveX object in JScript, an error is returned with no message and only a number: Error: Error number: -2146234304 A search on Google for the error number didn't return much. If we remove the strong name from the assembly, it works just fine. Any ideas on what could be the problem? Not

I followed this Stack Overflow post regarding how to create a project for VS2010, hoping that it would point me in the correct direction, but it doesn't cover creating a VS2012 project or solution. I also explored using SLNTools , but I don't see how to create a new solution from scratch. Ultimately, I would like to create 3-4 VS2012 projects programmatically and then add them to a solution which is also created programmatically. I attempted a solution based on this Stack Overflow post , but I get an odd error. Here is the code: Type typeDTE = Type.GetTypeFromProgID("VisualStudio.DTE.11.0");

When defining a COM-visible class in C++ I can define the supported threading model in the header file (the threading(single) line): [ coclass, default(IComInterface), threading(single), vi_progid("Example.ComClass"), progid("Example.ComClass.1"), version(1.0), uuid("72861DF5-4C77-43ec-A4DC-ED04396F0CCD") ] Is there a comparable way of setting the threading model in .NET (for example an attribute)? I currently define my COM-class as such: [Guid("67155A91-2948-43f5-B07F-5C55CDD240E5")] [ComVisible(true)] [InterfaceType(ComInterfaceType.InterfaceIsDual)] public interface IComInterface { ... }

In Windows API Code Pack for .NET Framework , many methods of COM Interop interfaces are decorated with MethodImplAttribute , for example: internal interface IShellItem { [PreserveSig] [MethodImpl( MethodImplOptions.InternalCall, MethodCodeType = MethodCodeType.Runtime)] HResult BindToHandler( [In] IntPtr pbc, [In] ref Guid bhid, [In] ref Guid riid, [Out, MarshalAs(UnmanagedType.Interface)] out IShellFolder ppv); Documentation for MethodImplOptions.InternalCall value says: The call is internal, that is, it calls a method that is implemented within the common language runtime. Documentation for

I am in the process of writing an application in C# which will open an Excel spreadsheet (2007, for now) via interop, do some magic, then close. The "magic" part is non-trivial, so this application will contain many references to many COM objects spawned by Excel. I have written this kind of application before (too many times, in fact) but I've never found a comfortable, "good smell" approach to interacting with COM objects. The problem is partly that, despite significant study, I still don't perfectly understand COM and partly that the interop wrappers hide much that probably shouldn't be