Hello,
I have questions regarding the above mentioned functoids

I want to know the best practices when to use custom functoid and when to us
e script functoid?

1. I can do my job using both and the question was what happens when i use c
ustom functiod and what happens if I use script functoid?
2. What are the pros and cons of using each one of them...etc.

Thank you in advance.

[ Post a follow-up to this message ]

The custom functoid can be reused across maps while the script only gives
you copy/paste reuse.

you might also get some benefits from using inline XSLT either way but I
haven't done any performance testing.

Matt


"Ashok" <Ashok@discussions.microsoft.com> wrote in message
news:B5C2631B-1C67-4D62-9F8B-072C2644B36D@microsoft.com...
> Hello,
> I have questions regarding the above mentioned functoids
>
> I want to know the best practices when to use custom functoid and when to
use script functoid?
>
> 1. I can do my job using both and the question was what happens when i use
custom functiod and what happens if I use script functoid?
> 2. What are the pros and cons of using each one of them...etc.
>
> Thank you in advance.
>

[ Post a follow-up to this message ]

Also, if you deploy your solution and you need to change the logic in your
code, using a custom functoid won't require you to recompile and redeploy
the solution.  If your script functoid is short and you don't need to reuse
it then you could use a scripting functoid instead.

Regards,
Tan Nguyen
Microsoft BizTalk Server

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------[vbcol=seagreen] 
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12
.phx.gbl[vbcol=seagreen] 
to[vbcol=seagreen] 
use[vbcol=seagreen] 

[ Post a follow-up to this message ]

Thank you for the information.

Just to clarify as i a new to Biztalk:
1. Use of external libraries inside the script functiod should solve the pro
blem of resue for me in case of script functoid. wont it?
i can reference the external routine in the script functoid.

2. could you please explain when you write i dont have to recompile and rede
ploy the solution in case of custom functoid...

3. could you talk about performance with respect to these two functoids?


"Tan Bao Nguyen" wrote:

> Also, if you deploy your solution and you need to change the logic in your
> code, using a custom functoid won't require you to recompile and redeploy
> the solution.  If your script functoid is short and you don't need to reus
e
> it then you could use a scripting functoid instead.
>
> Regards,
> Tan Nguyen
> Microsoft BizTalk Server
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> -------------------- 
> cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP
12
> .phx.gbl 
> to 
> use 
>
>

[ Post a follow-up to this message ]

Please clarify the following.
1. if i reference external libraries inside my script functoid..wont it solv
e the problem of reuse..so that i dont have to retype the whole code in ever
y script functoid that i want to use.
2. could you please explain when you write "custom functoid wont require me 
to recompile and redeploy the solution". if i make changes to code wont i ha
ve to rebuild it?
3. could you talk about performance aspects on using either of these functoi
ds.

thank you


"Tan Bao Nguyen" wrote:

> Also, if you deploy your solution and you need to change the logic in your
> code, using a custom functoid won't require you to recompile and redeploy
> the solution.  If your script functoid is short and you don't need to reus
e
> it then you could use a scripting functoid instead.
>
> Regards,
> Tan Nguyen
> Microsoft BizTalk Server
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> -------------------- 
> cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP
12
> .phx.gbl 
> to 
> use 
>
>

[ Post a follow-up to this message ]

Please clarify the following.
1. if i reference external libraries inside my script functoid..wont it solv
e the problem of reuse..so that i dont have to retype the whole code in ever
y script functoid that i want to use.
2. could you please explain when you write "custom functoid wont require me 
to recompile and redeploy the solution". if i make changes to code wont i ha
ve to rebuild it?
3. could you talk about performance aspects on using either of these functoi
ds.

thank you


"Tan Bao Nguyen" wrote:

> Also, if you deploy your solution and you need to change the logic in your
> code, using a custom functoid won't require you to recompile and redeploy
> the solution.  If your script functoid is short and you don't need to reus
e
> it then you could use a scripting functoid instead.
>
> Regards,
> Tan Nguyen
> Microsoft BizTalk Server
>
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
> -------------------- 
> cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP
12
> .phx.gbl 
> to 
> use 
>
>

[ Post a follow-up to this message ]

1. yes, this would do it for you.
2. If you have an external assembly for your logic, then you can make fixes
to that component and update it, sometimes, without having to update the map
compile and deploy it as well as any thing that depends on it like
orchestrations.
3. As I mentioned, I don't have any solid numbers on this, but you may want
to take a look at the performance guidelines on gotdotnet
http://www.gotdotnet.com/team/wsservers/

Matt


"Ashok" <Ashok@discussions.microsoft.com> wrote in message
news:588BA8B8-4711-49C2-88D4-8AA17B15655F@microsoft.com...
> Thank you for the information.
>
> Just to clarify as i a new to Biztalk:
> 1. Use of external libraries inside the script functiod should solve the
problem of resue for me in case of script functoid. wont it?
> i can reference the external routine in the script functoid.
>
> 2. could you please explain when you write i dont have to recompile and
redeploy the solution in case of custom functoid...[vbcol=seagreen]
>
> 3. could you talk about performance with respect to these two functoids?
>
>
> "Tan Bao Nguyen" wrote:
> 
your[vbcol=seagreen] 
redeploy[vbcol=seagreen] 
reuse[vbcol=seagreen] 
rights.[vbcol=seagreen] 
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12[vbcol=seagreen]
 
gives[vbcol=seagreen] 
I[vbcol=seagreen] 
when[vbcol=seagreen] 
i[vbcol=seagreen] 

[ Post a follow-up to this message ]

1) Yes.  You can reuse the same external library.
2) If you only change the code to the external library then you won't have
to rebuilt.  If you change your BizTalk project then you will need to
rebuild.
3) I beleive the performance should be about the same.  Note that we did
not do any performance testing regarding using scripts in external
libraries vs inline scripting in the functoid.

Regards,
Tan Nguyen
Microsoft BizTalk Server

This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------[vbcol=seagreen] 
<ueV$rt$cEHA.4048@TK2MSFTNGP12.phx.gbl>
<wJn$BlBdEHA.1540@cpmsftngxa10.phx.gbl>[vbcol=seagreen] 
solve the problem of reuse..so that i dont have to retype the whole code in
every script functoid that i want to use.[vbcol=seagreen] 
me to recompile and redeploy the solution". if i make changes to code wont
i have to rebuild it?[vbcol=seagreen] 
functoids.[vbcol=seagreen] 
your[vbcol=seagreen] 
redeploy[vbcol=seagreen] 
reuse[vbcol=seagreen] 
rights.[vbcol=seagreen] 
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12[vbcol=seagreen]
 
gives[vbcol=seagreen] 
but I[vbcol=seagreen] 
when[vbcol=seagreen] 
when i[vbcol=seagreen] 

[ Post a follow-up to this message ]