Yes, if have looked in MSDN, but i haven't found your link. Thanks for your answer:thumbsup:

I have been looking for an answer by google, but i got differnt answers, so i am hoping to get the ultimate answer here :-D What is the maximum size for a registry key of type REG_BINARY to read and write values in the windows registry ? Are there dependancies from the version of the os ?

I thought of something like this: http://msdn.microsoft.com/en-us/magazine/bb985086.aspx[^]

You can use the same Informations, OLEViewer uses for his visual representation of objects and interfaces. Is that what you are looking for ?

If you have timelimits in learning and implementing the task, you better should use a high-level COM-Wrapper like MFC oder ATL, then you must not implement the standard-interfaced like IUnknown or IDispatch youself. I think there must be lots of examples on codeproject. The error-message tells you to implement the function OnShowMessageDlg(). This is a function call from the com-server into your com-client, so you need an implementation.

Thanks for the tip. In the ...Designer.cs i modified Dispose

    /// <summary>
    /// Clean up any resources being used.
    /// </summary>
    /// <param name="disposing">true if managed resources should be disposed; otherwise, false.</param>
    protected override void Dispose(bool disposing)
    {
        if (disposing && (components != null))
        {
            components.Dispose();

            if (m\_Session != null)
            {
                while (true)
                {
                    if (Marshal.ReleaseComObject(m\_Session) <= 0)
                    {
                        m\_Session = null;
                        break;
                    }
                }
            }
            if (m\_System != null)
            {
                while (true)
                {
                    if (Marshal.ReleaseComObject(m\_System) <= 0)
                    {
                        m\_System = null;
                        break;
                    }
                }
            }

        }
        base.Dispose(disposing);
    }

but it doesnt't help, because the code isn't called at all, have i misunderstood you ?

If have tried Form_Closed and/or Form_Closing event to call Marshal.ReleaseCOMObject(). But it doesn't help,

At the end of the programm, INSIDE the COM-Component it is checked wether all references are "freed", this means if the refcounts are down to zero. The component is not only one single object, instead the library contains an object-hierarchy.

I have a simple C#-(Windows-)Application. The Main-Form has two COM-Members. Working with this variables is ok, everything works as expected. When i close the application by the menu, i call Close() in the event-handler and everything is ok, but when i close by systemmenu or alt-f4 i got a com-leak. What is the reason, what is missing ?

Google for "Registration-Free COM" you will find lots of information, mostly by microsoft. The "trick" is done by using manifests and activation contexts. :)

I have an application created with VS2005, consisting of some com-components created with VS2005. But one of the components is created by another department, so this component is still created with VS6. To find an error i have to debug from my application (VS2005) into this semi-external component(VS6). I have the symbols (.pdb) and the source files for the component and i succeed in stepping into the code of the component. But i can't watch any symbol. Has the PDB-format changed between this studio versions, are there any tricks to do the thing ?

I think you can't save this address, for example as a class member. If you add new elements to the vector it may need additional memory, which means he must allocate new memory for the whole vector and copy all his data. So every address to the old memory will be invalid afterwards.

I have an application(MFC), which should work with some "registration-free" com-components. I have extended the the application manifest and created a "com-manifest", as shown in the ms-examples. Everything works fine. BUT, one of my menuitems starts a userthread which needs one of the "registration-free" com-components, an ocx. The creation of the component succeeeds, but the QuickActivate() fails with an access violation. Some ideas what goes wrong? :sigh: Hoping for help, thank you.

Thank you very much for your answer. I have already seen you article and thats the reason i think it MUST work, somehow. But i don't see how to create a glass-toolbar in a dialog-based application. In your extension the function CreateAeroToolBarCtrl() is only available for WTL::CFrameWindowImpl. Maybe i miss a thing, but i can't see. Hoping for a (positive) response. :rose: :) :rose: JJ

Is it possible to give glass to ONE single control (toolbar,...) of a dialog-based application, which is otherwise "normal" ?? I am using WTL and ATL with VC 2005. Maybe this glass-control can be separated into an activex-control.

Where is the question/problem with COM. :confused:

As i can see, you want to pass a string, right ? Why don't use a "COM-String" ? [id(1), helpstring("method GetData")] HRESULT GetData([out, retval]BSTR* data); If you want to pass a "real" array, why don't you use a "COM-Array" ? [id(1), helpstring("method GetData")] HRESULT GetData([out, retval]SAFEARRAY* data);

My problem is not the function OleCreateLinkToFile() itself, but the resulting pointer. ppvObj [out] Address of pointer variable that receives the interface pointer requested in riid. Upon successful return, *ppvObj contains the requested interface pointer on the newly created object. Is there any way to get the interface-pointer to the "real" com-object itself. For example, if i open a word document can i get the interface-pointer of the shown word.document or running word.application starting from the ppvObj-pointer. My understanding of OLE is not good enough to see the right way (hope there is one :~ ).