I have multiple seperate projects under 1 solution folder, how can this  be deployed using BTDF

Can anyone share ideas and suggestions pl

Hi,

First add the BTDF project to the solution and specify the project details.

Then in the btdfproj file you can include the various projects present under the solution as follows:

<ItemGroup>
  <Schemas Include="$(ProjectName).Schemas.dll">
    <LocationPath>..\$(ProjectName).Schemas\bin\$(Configuration)</LocationPath>
  </Schemas>
</ItemGroup>
<ItemGroup>
  <Components Include="$(ProjectName).Utilities.dll">
    <LocationPath>..\$(ProjectName).Utilities\bin\$(Configuration)</LocationPath>
  </Components>
</ItemGroup>
<ItemGroup>
  <PipelineComponents Include="$(ProjectName).PipelineComponents.dll">
    <LocationPath>..\$(ProjectName).PipelineComponents\bin\$(Configuration)</LocationPath>
  </PipelineComponents>
</ItemGroup>
<ItemGroup>
  <Orchestrations Include="$(ProjectName).Orchestrations.dll">
    <LocationPath>..\$(ProjectName).Orchestrations\bin\$(Configuration)</LocationPath>
  </Orchestrations>
</ItemGroup>

For more details please refer:

http://www.tfabraham.com/BTDFDocs/V5_5/ConfiguringBizTalkArtifactsforDe.html

Thanks,

Raghav Ranjan

but this will effect every project...

for instance if there are separate projects A,B, C assigned to 3 developers and they should be under 1 solution.

So, if A is completed unit tested is up and running, but something fails in B Then whole solution breaks neither of the projects will work.

Is there any work around for this ?

Well, yes...but are you saying that Project A is test and deployed, then what if B breaks?

If A can be deployed separately from B, then they should be in separate Solutions.

My advice is always that a Solution is one Deployment unit, meaning all Projects in a Solution always go together, every time, even if not all have changed.

Well, yes...but are you saying that Project A is test and deployed, then what if B breaks?

If A can be deployed separately from B, then they should be in separate Solutions.

My advice is always that a Solution is one Deployment unit, meaning all Projects in a Solution always go together, every time, even if not all have changed.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator 5 hours 15 minutes ago

Well, yes...but are you saying that Project A is test and deployed, then what if B breaks?

If A can be deployed separately from B, then they should be in separate Solutions.

My advice is always that a Solution is one Deployment unit, meaning all Projects in a Solution always go together, every time, even if not all have changed.

• Marked as answer by Angie xuMicrosoft contingent staff, Moderator Wednesday, May 06, 2015 1:50 AM