Lodger
February 24th, 2007, 09:34 AM
Hi Gurus,
I wrote an simple COM server manually (no ATL) implementing IUnknown that uses the synchronous WinHttp (C++ API) to transmit multiple xml files to a web server. I didn't use ATL as I was still learning COM.
With that working successfully, I'd like to now port it to an IDispatch implemented ATL COM server, using asynchronous WinHttp with scripting support and events.
Being new(ish) to ATL I'm not sure how to handle asynchronous WinHttp in a COM environment, so I'm hoping to get some advice from you chaps that know?
Asynchronous WinHttp - What do I need to be aware of when implementing completion callbacks in COM environment?
MSDN - WinHTTP is not recommended for applications built on the Microsoft .NET Framework, because .NET Framework applications should use the networking facilities in the System.net classes. - Does this mean I can't use my component in a managed .NET application?
Any advice would be hugely appreciated :)
--L
I wrote an simple COM server manually (no ATL) implementing IUnknown that uses the synchronous WinHttp (C++ API) to transmit multiple xml files to a web server. I didn't use ATL as I was still learning COM.
With that working successfully, I'd like to now port it to an IDispatch implemented ATL COM server, using asynchronous WinHttp with scripting support and events.
Being new(ish) to ATL I'm not sure how to handle asynchronous WinHttp in a COM environment, so I'm hoping to get some advice from you chaps that know?
Asynchronous WinHttp - What do I need to be aware of when implementing completion callbacks in COM environment?
MSDN - WinHTTP is not recommended for applications built on the Microsoft .NET Framework, because .NET Framework applications should use the networking facilities in the System.net classes. - Does this mean I can't use my component in a managed .NET application?
Any advice would be hugely appreciated :)
--L