Biztalk Project Organization - Recommeded Practice

Question

Hello:
We are planning to leverage BizTalk pub/sub infrastructure to send (publish) and subscribe (send) messages. We have number of web services independently deployed
and maintained.  The service projects are organized in TFS under Main > Source. The Source folder contains the sub folders for each and every service. The existing structure looks like this
Root
Main
Source
Service A
Service B
Service B
Now that we will be using BizTalk as pub/sub infrastructure, we will have to create several BizTalk projects for the schemas, subscribers, maps, etc. The question
what’s the recommended practice to organize the BizTalk projects for the above Scenario? Does it make sense to create another folder under main for BizTalk and organize all BizTalk projects under it? Something like this:
 Root
Main
Source
BizTalk
Subscriber 1 // BizTalk subscriber project 1
Subscriber 2 // BizTalk subscriber project 2
Schemas // Holds all canonical schemas
Service A
Service B
Service B
Please advise the recommended practice

Answer 1

IMHO,  BizTalk projects also follow same semantics as other project types regarding TFS project structure. You might want to decide this based on how your teams are organized and manage work items etc. If you are using BizTalk 2009 or later, TFS Build
integration is available.
Here are some videos that you can have at,
http://www.cloudcasts.net/ViewWebcast.aspx?webcastid=2521312950167008799
http://www.cloudcasts.net/ViewWebcast.aspx?webcastid=2521072060555401694
http://msdn.microsoft.com/en-us/biztalk/ff603634
HTH.
Please mark it as answer by clicking on "Propose As Answer", if it helps. My Blog : http://dotnetizen.blogspot.com