|
Home > Archive > BizTalk Server General > April 2006 > Single Project vs Multi Projects
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Single Project vs Multi Projects
|
|
| SteveM 2006-04-27, 7:26 am |
| I'm interested to know what people think about developing their
orchestrations, schema, pipelines and maps in a single project versus
multiple projects.
Pros and cons would be helpful.
When developing multiple orchestrations in a single project (related but not
dependent), do you experience any trouble with strong naming and pipeline
confusion?
Is there a best practises around this and what do you think of those?
I've tried a couple of ways, but not totally convinced about either yet.
TIA
Steve
| |
| Eric Stott 2006-04-27, 7:26 am |
| I don't know if there is a 'best practices' approach to your situation, it
really requires some 'forward thinking' - meaning how often are you going to
need to be changing individual artifacts in each of the assemblies?
Also, if I know that I am going to be making a lot of changes to maps, but
the pipelines will rarely change, it is a good idea to have them in a
seperate assembly and reference them, as in BTS 2K4, it is a really time
consumer to constantly go in and change the pipeline to the default passthru
or XML for every map re-deploy.
There are benifits and drawbacks for each way, my suggestion is to keep
similar objects in the same assembly. If you are going to reuse artifacts
across multiple assemblies, then best to keep them seperated.
Eric
http://stottcreations.com/blog
"SteveM" <SteveM@discussions.microsoft.com> wrote in message
news:B43808EC-9503-4B53-B376-4855ECF081F2@microsoft.com...
> I'm interested to know what people think about developing their
> orchestrations, schema, pipelines and maps in a single project versus
> multiple projects.
>
> Pros and cons would be helpful.
>
> When developing multiple orchestrations in a single project (related but
> not
> dependent), do you experience any trouble with strong naming and pipeline
> confusion?
>
> Is there a best practises around this and what do you think of those?
>
> I've tried a couple of ways, but not totally convinced about either yet.
>
> TIA
> Steve
|
|
|
|
|