Re: Scripting Functoid: Inline or External Assembly?
From: Jon Flanders (jfland_at_develop.com)
Date: 01/12/05
- Next message: Sam Loveridge: "Re: Split, Substring and other functions in expression editor?"
- Previous message: Spaceman Spiff: "Scripting Functoid: Inline or External Assembly?"
- In reply to: Spaceman Spiff: "Scripting Functoid: Inline or External Assembly?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 11 Jan 2005 16:59:29 -0800
That doesnt' really matter since Functoids are just inline .NET code that
the Xslt Engine in .NET compiles into a .NET type.
here is my pro/con list
Inline:
Pro
- easier to setup
- easier deployment (only the map needs to be deployed - not the map and the
external assembly)
Con
- no intellisense in the editor
- no debugging
- limited namespaces
External
Pro
- Intellisense
- re-use (although if you have a re-usable piece of code you can make a
custom functoid)
- debugging
Con
- threading (the mapping engine pools these objects so your objects may be
accessed by multiple threads at the same time)
- deployment (must also distribute the assembly)
I am sure I've missed some but those are the ones I usually think about.
-- Jon Flanders [DevelopMentor] http://staff.develop.com/jfland/ http://www.develop.com/courses/biztalk "Spaceman Spiff" <SpacemanSpiff@discussions.microsoft.com> wrote in message news:CAD5DDA3-A3CF-48B5-8CA1-CA51D26FE641@microsoft.com... > Apart from better code maintence, is there any execution improvement in > calling an external assembly instead of having inline scripting? > Consider a situation where the Scripting Functoid is in a loop and it is > called hundreds of times. > > Regards > Spaceman Spiff
- Next message: Sam Loveridge: "Re: Split, Substring and other functions in expression editor?"
- Previous message: Spaceman Spiff: "Scripting Functoid: Inline or External Assembly?"
- In reply to: Spaceman Spiff: "Scripting Functoid: Inline or External Assembly?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
