com

I need to convert a CString instance into a properly allocated BSTR and pass that BSTR into a COM method. To have code that compiles and works indentically for both ANSI and Unicode I use CString::AllocSysString() to convert whatever format CString to a Unicode BSTR. Since noone owns the returned BSTR I need to take care of it and release it after the call is done in the most exception-safe manner posible and with as little code as possible. Currently I use ATL::CComBSTR for lifetime management: ATL::CComBSTR converted; converted.Attach( sourceString.AllocSysString() ); //simply attaches to

I am writing writing an API in COM in C++, and also writing a program which consumes this API in C#. My question is about BSTR memory management semantics when passing BSTRs into COM functions. Say my IDL looks like: HRESULT SomeFunction([in] BSTR input); Currently this function is implemented like this: HRESULT SomeFunction(BSTR input) { // Do stuff ..., then: SysFreeString(input); } When I call it from C# with something like SomeFunction(myString) , will C# generate something like this (pseudocode): myString = SysAllocString("string"); SomeFunction(myString); Or rather like this: myString =

Is there a way to get IntelliSense in own built COM classes in VBA? E.g. in the example below I would like to get "Number" showing up, whenever I press on the dot (or ctrl+space for shortcut): I suppose, if this is somehow resolved, I would also get some info concerning the public functions of the objects here: Thus, what are the suggestions? Suggestion 1 : Simple example could look like this. c# class library named IntellisenseDemo code using System; using System.Runtime.InteropServices; namespace IntellisenseDemo { [ComVisible(true)] [Guid("41B3F5BC-A52B-4AED-90A0-F48BC8A391F1")]

I have a .NET 4.0 library that uses Shell32 and Folder.GetDetailsOf() to get metadata from WTV files. I have used it successfully with Console and Windows Forms apps without issue. But for some reason, when calling the component from a .NET 4.0 Windows Service, the call to initiate the Shell class causes a COM error. The code that fails inside the library: Shell32.Shell shell = new Shell(); The error: Unable to cast COM object of type 'System.__ComObject' to interface type 'Shell32.Shell'. This operation failed because the QueryInterface call on the COM component for the interface with IID '

I believe that the only way to read an Outlook .msg file (in order to extra metadata like subject, attachments etc), is to use the Outlook API - the Application.Session.OpenSharedItem() method. If this is the case, then I am looking for way to run this code on our application server, which doesn't have MS OFfice or MS Outlook installed. I'm getting the error System.ArgumentException: progId not found. Outlook.Application Which of course is due to the absence of the Outlook application. Is there any way to install just a DLL or something in order to get the OpenSharedItem method to work? I don

how to iterate through C++ safearray pointer to pointer and access its elements. I tried to replicate the solution posted by Lim Bio Liong http://social.msdn.microsoft.com/Forums/en-US/vcgeneral/thread/022dba14-9abf-4872-9f43-f4fc05bd2602 but the strangest thing is that the IDL method signature comes out to be HRESULT __stdcall GetTestStructArray([out] SAFEARRAY ** test_struct_array); instead of HRESULT __stdcall GetTestStructArray([out] SAFEARRAY(TestStruct)* test_struct_array); Any ideas? thanks in advance Safearrays are created with SafeArrayCreate or SafeArrayCreateVector , but as you ask

What is the troubleshooting process for the "Retrieving the COM class factory for component with CLSID {XXXX} failed due to the following error: 80080005" errors in .Net? To clarify: I am getting this at runtime, on my XP machine, with client being .net code running under admin account. {XXXX} refers to one of our in-house COM components. From what I understand, 0x80080005 refers to "permission denied", but where do I go to check/change the permissions? Or am I completely wrong here, and the error is coming from the component itself, and not out of Windows COM subsystem? Seems to be a rather