Has anyone had any luck with this? I have tried to use manifest to isolate COM server (EXE) but no luck! I have read that out-of-process COM servers don't work with reg-free COM procedure of using manifests. The mt.exe command line switches you'll need to embed the manifest in your. My left foot is throbbing again after pasting that piece of MSDN prose. I really fealt like kicking Junfeng Zhang in the gnuts after reading that. Marshaling interfaces between processes and threads may not work as expected if you omit some of the dependencies for your component. If a file in the assembly implements a proxy stub, the corresponding file tag must include a subelement having attributes that are identical to a element. Marshaling though a type library is not something I've tried, you'd probably need the element in the manifest.įWIW, here's the horrid part from the MSDN docs: The MSDN documentation is horrid but it can be made to work. Use the and elements to name the proxy/stub DLL and its CLSID, the element to map the interface IIDs to the proxy/stub CLSID. GetModuleFileName() is the ticket to get the path.Īfter that, you'll only need a manifest to specify the CLSID of the proxy/stub DLL you'd need to marshal the interfaces. the same folder that contains the client. It might as well make the next step and start the.
It already knows to some degree because it specifies the CLSCTX_LOCAL_SERVER argument to CoCreateInstance(). exe to provide the required COM interfaces. But you'll be well on your way if your program knows it needs to start an out-of-process. Reg-free COM can't get the server started for you.
0 kommentar(er)
