01-31-06 11:59 PM
Right, you'll also have to register the assembly with the BizTalk
Management Database. Deploying it with the Deployment Wizard or BTSDeploy
will do the trick. You should also have the assembly in the GAC. If all
else fails, try bouncing the BizTalk host instance service.
HTH,
Doug Girard [MSFT]
Note: This posting is provided "AS IS" with no warranties, and confers no
rights.
--------------------
>From: "Greg Forsythe" <greg.forsythe@gmail.com>
>References: <DDD4101B-3373-4027-A9E2-D5BF2CB5458F@microsoft.com>
>Subject: Re: Building a Pipeline
>Date: Wed, 25 Jan 2006 11:16:10 +1300
>Lines: 19
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.3790.1830
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>X-RFC2646: Format=Flowed; Original
>Message-ID: <OO1m7PTIGHA.1180@TK2MSFTNGP09.phx.gbl>
>Newsgroups: microsoft.public.biztalk.general
>NNTP-Posting-Host: 219-88-216-7.jetstream.xtra.co.nz 219.88.216.7
>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
>Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.biztalk.general:34281
>X-Tomcat-NG: microsoft.public.biztalk.general
>
>You have created a Biztalk Assembly that needs to be deployed via Biztalk
>Deployment Wizard or BTSDeploy.exe
>rather than just added to the GAC
>
>Greg
>
>
>
>"Bakunin" <Bakunin@discussions.microsoft.com> wrote in message
>news:DDD4101B-3373-4027-A9E2-D5BF2CB5458F@microsoft.com...
appear[vbcol=seagreen]
>
>
>
[ Post a follow-up to this message ]
|