Dog vil jeg påpege at i større systemer er det ikke altid blot at gøre dette, når mange forskellige typer af teknologi indgår (for slet ikke at tale om “politiske” beslutninger). Det betyder dog ikke at man internt i et system kan integrere med CDM.

I would not recommend using the mapper to generate your initial xslt document, because:
1) The xslt generated by the BizTalk mapper is very bad structured
2) Namings are bad
3) The effort in making the XSLT from scratch is so small(4 or 5 lines), but the gain is so big, given that you know exactly what’s going on.

In regards to XSLT 2.0 support, that’s really a .NET/Microsoft question more than a BizTalk related question. To my knowledge Microsoft has no plans to include XSLT 2.0 support.

To speed up the initial custom xslt I start out using the mapper to do the basic linking of fields and looping of records. When validating the map, you get custom xslt including the simple mapping and the namespaces. Save the output and you get a first version to work with.

I like your idea with using external assemblies as reusable code when you realize you are using the same inline code over and over again.

Do you know when Microsoft will support xslt 2.0 in the mapper?

Cheers
/Willem

God weekend

/Thomas