hi,
I am working on a complex project and I need some advise.
we are thinking to put schemas, piplines, orchestartions and maps in
their own projects.

Any guidence on this? should I do that or not?

I think there will be scenarios when I need to have maps in say
orchestration, like when I am communicating with webservices then I
need to have maps in the same project as orchestration is.

Any help will be highly appreciated.

Regards,
Billa

[ Post a follow-up to this message ]

I would break up the projects.

You can put maps and schema together if you want.  You would want to
separate then out in a logical way, in a way that will promote easy reuse
later.  This might be maps and schema in separate projects or VendorA maps
and schemas together separate from VendorB.

Typically you want Orchestrations and Pipelines in completely separate
projects and not together with schema and maps.  If you need a map, then jus
t
add a reference to the maps/schema projects.

There are some important reasons to break up the projects and in some cases
things will not work correctly if they are in the same project (like having 
a
custom pipeline using schemas in the same project).

This thread also talks about this topic:
http://www.biztalkgurus.com/forums/viewtopic.php?t=249

Hope this helps.

Stephen W. Thomas
http://www.biztalkgurus.com
http://geekswithblogs.net/sthomas/


"Billa" wrote:

> hi,
> I am working on a complex project and I need some advise.
> we are thinking to put schemas, piplines, orchestartions and maps in
> their own projects.
>
> Any guidence on this? should I do that or not?
>
> I think there will be scenarios when I need to have maps in say
> orchestration, like when I am communicating with webservices then I
> need to have maps in the same project as orchestration is.
>
> Any help will be highly appreciated.
>
> Regards,
> Billa
>
>

[ Post a follow-up to this message ]

Thanks a lot!

[ Post a follow-up to this message ]