Hello,

We put schema, map, pipeline, and orchestration in different projects. We
found that any of the assembly can be updated and replaced without deploying
the whole set of asseblies. Say, we can upgrade schema.all without changing
the map.dll, which depends on schema.dll.

Does anyone know how to explain that situation? Is it by BizTalk's design.
As far as I know, the map.dll should also be graded if the schema.dll
changes.

Regards,

Poon, Chak Yau.

[ Post a follow-up to this message ]

If you are not changing version numbers on your projects, then the
references will still hold.  However, if you change your interfaces, or in
this case schemas, you run the risk that your map won't work because it was
built against the old structure.  This is a .Net issue, not a biztalk
specific issue.  You are right, if you change a schema that a map depends
on, you should rev both.

Matt

"Quink Poon" <quinkpoon@hotmail.com> wrote in message
news:O4RgTYmdEHA.3016@tk2msftngp13.phx.gbl...
> Hello,
>
> We put schema, map, pipeline, and orchestration in different projects. We
> found that any of the assembly can be updated and replaced without
deploying
> the whole set of asseblies. Say, we can upgrade schema.all without
changing
> the map.dll, which depends on schema.dll.
>
> Does anyone know how to explain that situation? Is it by BizTalk's design.
> As far as I know, the map.dll should also be graded if the schema.dll
> changes.
>
> Regards,
>
> Poon, Chak Yau.
>
>

[ Post a follow-up to this message ]