I’ll take this as a challenge, and will bet the fastest way to shuffle your data between Excel and C# is to use Excel-DNA – http://excel-dna.net. (Disclaimer: I develop Excel-DNA. But it’s still true…) Because it uses the native .xll interface it skips all the COM integration overhead that you’d have with VSTO or another … Read more
Add reference to Microsoft.VisualBasic.dll and then: Microsoft.VisualBasic.Information.TypeName(someCOMObject) MSDN reference here.
For Microsoft Office 365 in Windows 10 I was running Microsoft Office 365 with Windows 10 and tried the mentioned solutions to remove the registry key without success. I went to Settings -> Apps in an attempt to repair the Office 365 suite: To get there you can follow these steps: Open Start Select Settings … Read more
Are there any disadvantages using the IDisposable Interace Sure, it accomplishes absolutely nothing. Using Using or calling Dispose() is never an appropriate way to set a variable to Nothing. Which is all that your code does. We completely avoid to use the two dot rule. Feel free to continue to ignore it, it is nonsense … Read more
I was trying to do similar thing. I concluded that the COM library provided by Microsoft is incomplete. I don’t use it because the doc mentioned that “Note: This topic is pre-release documentation and is subject to change in future releases”. So, I decided to take a look at what IISExpressTray.exe is doing. It seems … Read more
It does the same thing as running Regasm.exe with the /tlb and /codebase options. The /codebase option is probably the one you forgot. Regasm likes assuming you put the DLL in the GAC and generates a warning when you don’t. The GAC is indeed a very good way to avoid DLL Hell, always a COM … Read more
“Make assembly COM visible” is a big hammer to make all public types in the assembly [ComVisible]. Rarely desirable, you will want to select the specific types that you want to be visible, like you did in your snippet. After the assembly is built, it needs to be registered so that a COM client can … Read more
This is the answer I wanted to find in StackOverflow but couldn’t. It turns out to be fairly easy to turn a simple C# dll into a COM dll. To create the C# dll Create a solution with a C# class project. The class should have an interface for the properties/methods and an interface for … Read more
I know this is old, but there’s an easier way than the listed. This works when you reference two assemblies that share types with the exact same name and namespace. If you right-click on the Reference to your DLL and select Properties, you will see that here’s a property called “Aliases” The default value is … Read more
The best explanation I’ve seen is in Chapter 7 of the free Foundations of Programming e-book. Basically, in .NET a memory leak occurs when referenced objects are rooted and thus cannot be garbage collected. This occurs accidentally when you hold on to references beyond the intended scope. You’ll know that you have leaks when you … Read more