| Paul Somers 2006-04-27, 7:25 am |
| Are you talking BizTalk 2004 or 2006?
In a production, or test environment this is a must, you should deploy your
solution to the other machine.
You should export the bindings, and copy and gac(some of them) BizTalk
assemblies and all other dependant assemblies.
These get deployed to the destination BizTalk machine. There are a number of
tools to make this easier, the one out of the box is the BizTalk deployment
tool.
I use my BizTalk Administration Tool for this, it does it all, however if
you wish to get more fancy then you can use deployment scripts to script
this for future deployments.
Something you need to prepare and plan for.
With 2006 it's a bit easier, you export the application it goes and figures
out what it needs, and you add anything it did not get, documented in the
help. The problem here is the bindings for each environment may be different
you need to supply separate bindings for each environment you deploy to,
hence the need for scripting still.
Paul.
"RedStain" <RedStain@redstain.com> wrote in message
news:%23BfEGZ4ZGHA.1352@TK2MSFTNGP05.phx.gbl...
> SUMMARY: How do I install visual studio on one machine yet create
> applications and deploy Biztalk solutions on another machine with Biztalk
> Server.
>
> Additional Notes: Sorry this is a simple question but has to be asked. I
> am currently using a single server solution for evaluation. And I want to
> build my first Test environment with distributed kit. Is there any
> 'gotchas' to remember when deploying VStudio and Biztalk on separate
> boxes? Documentation links will be happily accepted 
>
>
|