com

My question is similar to Getting CLSID for a DLL file? , I think. I have a directory with some DLLs, each one implementing one or more COM interfaces. I would like to get: 1) Each interface name 2) The CLSID of the class implementing the interface For each DLL. It's important that everything can be done programatically (So I can't use some sort of COM browser and manually look up for that information). Later I will lookup the CLSID given the interface name and call some methods using IDispatch. One alternative seems to be scanning the registry trying to match the type, interface and class

I know that COM provides reusability at the binary level across languages and applications. I read that all components built for COM must adhere to a standard memory layout in order to be language-independent. I do not understand what "standard memory layout" means. What makes COM language-independent? stakx First, some technical background : C++ compilers usually generate something called a "vtable" for any class with virtual functions. This is basically a table of function pointers. The vtable contains a function pointer to every virtual method implemented by a class. In COM, interfaces are

I am new to COM and trying to understand the difference between STA and MTA. I tried to create an example that would show that COM can manage calls to object created in STA that is not thread-safe. MyCalcServer class here is created using ATL Simple Object. The settings used are the same as in this article : Threading Model: Apartment Aggregation: No Interface: Custom MyCalcServer COM object is used in another C# project which is: class Program { [STAThread] static void Main(string[] args) { MyCOMLib.MyCalcServer instance = new MyCOMLib.MyCalcServer(); string output1; instance.ChangeValue(

Say I have a C# Nullable DateTime? property that needs to be consumed by VBA through COM. public DateTime? TestDate { get ; set; } Unfortunately, Nullables are not visible through COM, so I would like to have the property return a something that will be seen as a Variant from VBA. Unfortunately, I'm not sure how this should be written. I tried using an object and a dynamic instead of DateTime? : while I can get the property value, I can't set it (I get Run-Time error '424' Object required errors from VBA). Note : I don't have issues with making my library COM Visible: everything works fine and

I'm writing Python 2.6 code that interfaces with NI TestStand 4.2 via COM in Windows. I want to make a "NAN" value for a variable, but if I pass it float('nan') , TestStand displays it as IND . Apparently TestStand distinguishes between floating point "IND" and "NAN" values. According to TestStand help : IND corresponds to Signaling NaN in Visual C++, while NAN corresponds to QuietNaN That implies that Python's float('nan') is effectively a Signaling NaN when passed through COM. However, from what I've read about Signaling NaN , it seems that Signaling NaN is a bit "exotic" and Quiet NaN is

How do I create a dynamic COM/OLE/ActiveX object in C# 4.0 from a program identifier or ProgID (such as "Word.Application") without referencing a library? In C# 3.5 I'd have to write something like Type comObjectType = Type.GetTypeFromProgID(progId, true); Activator.CreateInstance(comObjectType); Is there an easier way to do it in C# 4.0 so I can assign it to a variable of type dynamic (using the dynamic keyword)? What's wrong with dynamic myTypeInstance = Activator.CreateInstance(Type.GetTypeFromProgID(typeName, true)); ? If it's a known type name, there's also dynamic myTypeInstance =

I've added an .ocx to the toolbox in VS. Two .dll's were created: Interop.NNN.dll, AxInterop.NNN.dll. What is each one? Are they both required? The AxFoo.dll assembly contains an automatically generated class that's derived from the System.Windows.Forms.AxHost control. It is pretty simple, it has methods, properties and events, the same ones you have available in the .ocx, that simply call the Foo.dll interop library. So, yes, you definitely need to deploy both assemblies. Interop.xxx.dll and AxInterop.xxx.dll are runtime callable wrappers (RCW) for a referenced COM and an ActiveX dll

I realise it's an early release and unstable. I wouldn't dream of swapping out the default webbrowser control for IE9 in any other project, but in this case I specifically need IE9 to compare alongside other versions. I'd like to have the .NET WebBrowser control use IE9 instead of the default version of IE on the machine. I have full control of the machine so it's no problem to hack away at system files or whatever else may be necessary. Normally, this could be achieved by installing the update to IE, but in IE9's case, it installs a separate application, leaving the current version of IE