Sorry if this sounds like a newbie question, i have just been reading throug
h
the BLog white paper on adapter implementation and although there may be an
obvious answer, if like to know if the base Adapter components in BT2004 are
implemented in COM as interfaces are accessed using the classic COM QI ... i
s
this the case, i thought BT2004 was wholly written in c# and if so is it the
case that the COM components were also written in c# using the interop ???

[ Post a follow-up to this message ]

Hello,

>Sorry if this sounds like a newbie question, i have just been reading throu
gh
>the BLog white paper on adapter implementation and although there may be an
>obvious answer, if like to know if the base Adapter components in BT2004 ar
e
>implemented in COM as interfaces are accessed using the classic COM QI ... 
is
>this the case, i thought BT2004 was wholly written in c# and if so is it th
e
>case that the COM components were also written in c# using the interop ???

Parts of BizTalk are built as COM objects, the traditional way (QI as you me
ntion).
Part of BizTalk are built using .NET.

This is not secret, you can see some COM interfaces (documented below) .more
over, when debugging your adapter, there are changes that
you will attach a debugger to BTSNTSVC.EXE. You can use the debugger to figu
re out which module contains which kind of code (native or .NET)..

http://msdn.microsoft.com/library/e...br />
ame=true (IBaseMessage)
http://msdn.microsoft.com/library/e....asp?frame=true (IBTBatchTransmitter)

When you write adapters or pipelines in .NET, the messaging engine's behavio
r is to sometimes host the CLR and run your component inside
as well as sometimes doing COM interop with your component.

Of course, you should not depend on any of these internal details since they
 are subject to change.

Thanks,
-GIlles.

[ Post a follow-up to this message ]