Hi Schemer,
The v2.0 hosting APIs are really all about using the AppDomainManager which
will get loaded into your process. You can have the AppDomainManager
P/Invoke back into your host and pass a delegate out that you can then call
(just make sure to pin it if you're going to keep it alive for longer then
the duration of the call).
Alternately you could look at
System.Runtime.InteropServices.Marshal.GetFunctionPointerForDelegate and
GetDelegateForFunctionPointer to marshal by hand delegates back and forth
between the two sides.
A more general way is through a COM interface implemented by a managed
type. You create an instance of the type by calling
AppDomain.::CreateInstanceAndUnwrap(), then QueryInterface for the COM
interface, and do normal COM method calls on it.
Thanks.
Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx. ==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.