In one C# project, I get the following warning: warning CS1762: A reference was created to embedded interop assembly \'Interop.SomeLibrary.dll\' because of an indirect reference to that assembly cre
It looks like SaveAs has gone away in Office 2010 in favor of SaveAs2. What is going on here? Are there any important differences between开发者_开发知识库 the two? My fix has been to check for SaveAs2
Hi I have a COM DLL implemented in ATL and now I want to develop a test exe in C# to test the features.
In the IDL file for a C++ component I have something like the following, allowing the property to be COM visisble:
I am supporting a legacy ASP page which creates an ADODB stream object like this, then attempts to set it\'s type with an ADODB enumerator.
I have an application (Delphi Native code) that needs to access a .NET assembly (exposes a few COM classes. I want to do this using side by side assemblies and manifests. I have done this with a test
Here\'s the setup: I have two bluetooth devices paired with a single PC. Both are SPP, intended to be used with separate virtual COM ports. One device is assigned COM9, the other is assigned COM11. If
We have COM dll which was written in C++ and has been used by the apps written in vb 6.0. My company plans write the newer version开发者_运维知识库s of apps in .Net platform.
I have a CLSID and I need to instantiate this in a Different server (i.e. DCS ) where as my working machine is (i.e. MWS ).
This is a variation on another Q of mine. I have two applications, X and Y. They have to share a single COM object between them. X will be sending data to this object and Y will respond on events sent