How to set up a Biztalk environment with multiple developers?

If we have 3 developers working on the same Biztalk project, what is the best way to customize our development environment?

We use TFS to store the Biztalk project.

Should we use 1 sql server and 1 Biztalk server, and then have 1 or more development machines that access sql and biztalk servers? The problem we are facing is when 1 developer compiles and deploys his changes, he can influence other developers if they also try to compile and deploy their work.

Should we have each developer host their own sql and biztalk server for local development, either on their own machine or on their own virtual machine? The problem we are facing is that each developer can change their server settings, and these settings are not saved in the original control. This can be confusing when deploying changes to the test server. Another small problem is that every developer will need a sql server, a biztalk server and a Windows server.

Is there any other way to set up a biztalk development environment with multiple developers?

+5
source share
2 answers

, BizTalk . , , , // .

, /, , .

- , . , . , , (dev, test, production ..).

+20

tomasr . , , , . , , , , , - , . , , , , BizTalk, MSI, . , , , , #, , . CruiseControl.net, Nant, nunit , , , , , BizTalk, .

+2

All Articles