I\'m hosting a .NET library in my C++ program using the following methods, though not an exhaustive list:
Folks - I\'m creating many COM servers (I\'m launching开发者_运维问答 numerous EXEs) in .net, talking to COM via COM -interop, using numerous COM objects in the server, etc.If I kill the process, is t
Recently, I am facing an issue I thought it would be easy to implement. I have a COM object already installed on my Windows 7 machine.
Trying to 开发者_运维知识库make an excel file using this code: app = new Excel.Application(); app.Visible = false;
I found an out-proc COM server implemented (supposedly due to a bug) in such way that if a client calls CoGetClassObject() and then never tries to instantiate anything with the retrieved factory the s
I stumbled upon this while trying to build an ActiveX dll from an old (but still maintained) VB6 exe project(*) sources in order to perform some testing via COM / NET interop.
MSDN says CoRevokeClassObject() informs COM that some COM class is no longer available for instantiation.
I am trying to programtically enable a deskband that I wrote usingthis from code project. The deskband works fine, and I have corrected the problem with the IStream interface that prevents the toolbar
I need to automate office documents (Word & Excel) from my .Net4 a开发者_运维技巧pp. Since I can\'t really force my users to use a specific Office version I don\'t use interop assemblies or tlbi
I need to run some native C++ code in such way that if it crashes it doesn\'t affect my C# progr开发者_开发知识库am. I can use an out-proc COM server with \"single use\" activation so that each COM ob
加载中,请稍侯......