hi,

there are two clients that we deal with. two classes have been defined for
the purpose of defining methods to be used in the mapper scripts for each of
the clients. the problem is, any change required to any method requires the
class to be compiled, which "resets" the script functoids' settings,
whereever such a functoid is being used. this makes fixing the mappers after
any change a very tedious task. would it be a better option to define custom
functoids (i'll have to define a bunch of these though) instead? what's
involved in deploying a custom functoid, and in modifying one?

[ Post a follow-up to this message ]

Why does it reset the script's functoids settings?  Are you chaning the .NET
version number of the component?

--
Jon Flanders [DevelopMentor]
http://staff.develop.com/jfland/
http://www.develop.com/courses/biztalk
"biztalker" <biztalker@discussions.microsoft.com> wrote in message
news:21EF04BE-F99F-4C42-839B-9FD32B32BA7D@microsoft.com...
> hi,
>
> there are two clients that we deal with. two classes have been defined for
> the purpose of defining methods to be used in the mapper scripts for each
of
> the clients. the problem is, any change required to any method requires
the
> class to be compiled, which "resets" the script functoids' settings,
> whereever such a functoid is being used. this makes fixing the mappers
after
> any change a very tedious task. would it be a better option to define
custom
> functoids (i'll have to define a bunch of these though) instead? what's
> involved in deploying a custom functoid, and in modifying one?

[ Post a follow-up to this message ]

i'm not sure if the version change takes place everytime the component is
rebuilt. i don't change the version number myself. does it take place
automatically?

"Jon Flanders" wrote:

> Why does it reset the script's functoids settings?  Are you chaning the .N
ET
> version number of the component?
>
> --
> Jon Flanders [DevelopMentor]
> http://staff.develop.com/jfland/
> http://www.develop.com/courses/biztalk
> "biztalker" <biztalker@discussions.microsoft.com> wrote in message
> news:21EF04BE-F99F-4C42-839B-9FD32B32BA7D@microsoft.com... 
> of 
> the 
> after 
> custom 
>
>
>

[ Post a follow-up to this message ]

It does if you use the 1.0.* default value for the AssemblyVersion attribute
in your AssemblyInfo.cs (or vb) file.  Change it to 1.0.0.0 and you won't
have to rebuild your map every time.

--
Jon Flanders [DevelopMentor]
http://staff.develop.com/jfland/
http://www.develop.com/courses/biztalk
"biztalker" <biztalker@discussions.microsoft.com> wrote in message
news:79B2823C-D39F-482A-BA7F-C7A236CD635C@microsoft.com...[vbcol=seagreen]
> i'm not sure if the version change takes place everytime the component is
> rebuilt. i don't change the version number myself. does it take place
> automatically?
>
> "Jon Flanders" wrote:
> 
.NET[vbcol=seagreen] 
for[vbcol=seagreen] 
each[vbcol=seagreen] 
requires[vbcol=seagreen] 
what's[vbcol=seagreen] 

[ Post a follow-up to this message ]

oh...so it was the asterisk causing that trouble...sheesh
thanks a lot Jon.

"Jon Flanders" wrote:

> It does if you use the 1.0.* default value for the AssemblyVersion attribu
te
> in your AssemblyInfo.cs (or vb) file.  Change it to 1.0.0.0 and you won't
> have to rebuild your map every time.
>
> --
> Jon Flanders [DevelopMentor]
> http://staff.develop.com/jfland/
> http://www.develop.com/courses/biztalk
> "biztalker" <biztalker@discussions.microsoft.com> wrote in message
> news:79B2823C-D39F-482A-BA7F-C7A236CD635C@microsoft.com... 
> ..NET 
> for 
> each 
> requires 
> what's 
>
>
>

[ Post a follow-up to this message ]