I am in the middle of implementing a BizTalk project involving an
orchestration which consumes a web service A (implemented by me). This
orchestration is exposed as a second web service B.

Both the BizTalk project and the web service A are at the
implementation stage and every time I do any changes in the web
service, I update the reference to it from the BT-project, recompile
the BT-project and redeploy the BT-project. Naturally I find this very
troublesom. Is it really necessary? I do this because I am not
confident that it is really enough to just re-compile the web-service.

[ Post a follow-up to this message ]

Hello anetasalomonsen@hotmail.com,

You only have to update the reference to your webservice when the interface
of the webservice (WSDL) has changed.
For the biztalk part you don't have to redeploy every time. You can used
recompile the assembly that contains your orchestration, (re)put in in the
GAC and stop and start the biztalk host.

Here is a tool for stopping and starting the host: http://biztalkia.blogspot.com/2

Another handy thing for putting your assembly in the gac: http://biztalkia.blogspo
t.c...dll-to-gac.html

HTH,
Randal van Splunteren
http://biztalkia.blogspot.com


> I am in the middle of implementing a BizTalk project involving an
> orchestration which consumes a web service A (implemented by me). This
> orchestration is exposed as a second web service B.
>
> Both the BizTalk project and the web service A are at the
> implementation stage and every time I do any changes in the web
> service, I update the reference to it from the BT-project, recompile
> the BT-project and redeploy the BT-project. Naturally I find this very
> troublesom. Is it really necessary? I do this because I am not
> confident that it is really enough to just re-compile the web-service.
>

[ Post a follow-up to this message ]

Thank you so much for these very helpful links!!!

[ Post a follow-up to this message ]