CODEWITHSUNDEEP
biztalkbiztalk-2013
user3447261
user3447261

Reputation: 41

BizTalk common schema

As per best practice I have separated my BizTalk solution into projects based on artifacts (schema, pipelines, maps etc). I've also separated business processes into solution folders. I have created a common project to hold schema that need to be available for each and referenced these when needed... so far so good.

When I deploy it will deploy the common schema and each reference - resulting in multiple schemas. If I try to untick the dependency in the project assembly I get the error

This dependency was added by the project and cannot be removed.

Am I missing something?

Visual Studio 2012, BizTalk Server Dev Ed 2013.

Upvotes: 2

Views: 417

Answers (1)

DTRT
DTRT

Reputation: 11040

Really, same answer as in the other post.

Consider the Visual Studio Solution as one Deployment Unit and build your processes around that. Meaning, all the Projects, Schemas, Maps, Orchestrations, would always go out together even if only one changed.

I try really hard to not share Schemas across Solutions specifically because of the Deployment issues. I do this even if it means duplicate or essentially duplicate Schemas. 99% of the time, the only thing that breaks is the automatic Schema resolution in the Xml Disassembler and that is easily solvable.

"When I deploy it will deploy the common schema and each reference - resulting in multiple schema"

Sorry, this part doesn't seem right. If you have a common Schema project, there shouldn't be duplicates.

Upvotes: 1

Related Questions