I\'m porting a C# library to COM and I\'m having a hard time trying to translate some delegates. The C# library works with some callbacks (using delegates). Usually I would translate that to events to
I executed the following C# code to Test environment and PROD server: This code checks if it is able to instantiate COM classes on the servers:
Well, I\'m trying to call functions in the AET60.dll, which contains the API for AET60 BioCARDKey (finger print and smart card reader) with c#; actually, I have succesfully called almost every functio
When the Register for COM Interop option in the build properties is checked, I get an error: Canno开发者_如何学运维t register assembly -access
I am getting this stacktrace: System.Runtime.InteropServices.COMException (0x800A13E9): Word ðú÷ì ááòéä.
I have an asp.net app which uses legacy COM interop library.Works fine until mem开发者_运维知识库ory reaches somewhere around 500Mb and then it is no longer able to create new COM objects (get various
I have a .Net asm with several interfaces and classes exposed to COM using the [ComVisible(true)] attribute.I generate a tlb, then reference this in my StdAdx file within a C++ COM component.What\'s o
i am working on an application which calls the COM component of a partner\'s application. Ours is .Net, theirs isn\'t. I don\'t know much about COM; I know that the component we\'re calling is late-bo
I have an assembly on a shared folder (UNC-path only, no mapped drive).When I try to register it programmatically via RegistrationServices, I\'m getting a strange error.
The short version I\'ve got a Word Addin in VB.net and VSTO that exposes a COM compatible object via Word.COMAddins.Object, so that the addin functionality can be called External to Word, without acce
加载中,请稍侯......