|
Home > Archive > BizTalk Server Orchestration > March 2004 > Orchestration issue in 2004
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Orchestration issue in 2004
|
|
| Sharon 2004-03-29, 9:59 am |
| I am using a .net component in Orchestration. I have
the .net component in GAC. Whenever i update the .Net
component it is not reflecting automatically in the
Orchestration. sometimes it throws exception that it can't
find the assembly.
My question is whether it is required to recompile the
orchestration when i change the .Net component. whether
there is anyway i can maintain the compatability without
recompiling the Orchestration.
Thanks
Sharon
| |
| Tomas Restrepo \(MVP\) 2004-03-29, 9:37 pm |
| Sharon,
> I am using a .net component in Orchestration. I have
> the .net component in GAC. Whenever i update the .Net
> component it is not reflecting automatically in the
> Orchestration. sometimes it throws exception that it can't
> find the assembly.
>
> My question is whether it is required to recompile the
> orchestration when i change the .Net component. whether
> there is anyway i can maintain the compatability without
> recompiling the Orchestration.
Yes, there certainly is. For strong named components, versioning is done
according to the version number. Keep it the same (well, almost, there's a
few cases where you can avoid that) and you should be OK (as long as the
public interface is the same).
That said, you might need to restart the biztalk application host service
for it to grab the updated assembly...
--
Tomas Restrepo
tomasr@mvps.org
| |
| Sharon 2004-03-30, 10:07 am |
| Thanks Tomas. This info really helps.
Sharon
>-----Original Message-----
>Sharon,
>
can't[color=darkred]
>
>Yes, there certainly is. For strong named components,
versioning is done
>according to the version number. Keep it the same (well,
almost, there's a
>few cases where you can avoid that) and you should be OK
(as long as the
>public interface is the same).
>
>That said, you might need to restart the biztalk
application host service
>for it to grab the updated assembly...
>--
>Tomas Restrepo
>tomasr@mvps.org
>
>
>.
>
|
|
|
|
|