|
Home > Archive > BizTalk Server Orchestration > October 2004 > Does newer version of Assembly will be used?
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 |
Does newer version of Assembly will be used?
|
|
| John Lee 2004-10-15, 9:09 pm |
| Hi,
I have an orchestration that use a component MyComp.dll version 1.0.0.0 - I
deployed the orchetration and everything works fine  now a newer version
of the MyComp.dll deployed on biztalk and has fixes but interface did not
change - How can I make the orchestration to use the newer version of the
MyComp.dll? I tried to put a Orchestration.dll.config and use
<runtime><redirect but no luck -
Any help and tips are greatly appreciated!
John
| |
| Sachin Surana 2004-10-15, 9:09 pm |
| Hi John,
Try putting the redirection in config file of BTS i.e BTSNTsvc.exe.config.
Also, let me know if it worked
Cheers,
Sachin
"John Lee" wrote:
> Hi,
>
> I have an orchestration that use a component MyComp.dll version 1.0.0.0 - I
> deployed the orchetration and everything works fine now a newer version
> of the MyComp.dll deployed on biztalk and has fixes but interface did not
> change - How can I make the orchestration to use the newer version of the
> MyComp.dll? I tried to put a Orchestration.dll.config and use
> <runtime><redirect but no luck -
>
> Any help and tips are greatly appreciated!
>
> John
>
>
>
| |
| Matt Milner 2004-10-15, 9:09 pm |
| I belive I read a post here from a MS person that version redirection does
not work in BTS. I think you'll have to update your orchestration assembly
with the new reference and redeploy it.
Please do try the other suggestion here and let us know if it worked, but
don't be surprised if it doesn't.
Matt
"John Lee" <john.nospam@pursca.com> wrote in message
news:%23qpQTgYsEHA.3564@tk2msftngp13.phx.gbl...
> Hi,
>
> I have an orchestration that use a component MyComp.dll version 1.0.0.0 -
> I deployed the orchetration and everything works fine now a newer
> version of the MyComp.dll deployed on biztalk and has fixes but interface
> did not change - How can I make the orchestration to use the newer version
> of the MyComp.dll? I tried to put a Orchestration.dll.config and use
> <runtime><redirect but no luck -
>
> Any help and tips are greatly appreciated!
>
> John
>
| |
| John Lee 2004-10-15, 9:09 pm |
| Yes, when I move the <runtime> bindingRedirect into BTSSvc.exe.config and it
worked!!! But mess around with this configuration file is kinda scary though
Thanks Sachin!
John
"Sachin Surana" <SachinSurana@discussions.microsoft.com> wrote in message
news:482BB7E6-5C0C-4307-AB06-1E04B12BF91E@microsoft.com...[vbcol=seagreen]
> Hi John,
>
> Try putting the redirection in config file of BTS i.e BTSNTsvc.exe.config.
> Also, let me know if it worked
>
> Cheers,
> Sachin
>
> "John Lee" wrote:
>
| |
| Sachin Surana 2004-10-15, 9:09 pm |
| Agreed, this is not a clean solution. There could be a few other options as
well...
1) From the .NET configuration interface, you can add a library to the
'configured assemblies' in GAC and change its binding policy to redirect it
to a new version. This is cleaner than the previous approach as it becomes
assembly specific and not application specific.Please let me know if, if you
know how to configure assemblies while instaling it. We would certainly not
like to do it through GUI.
2) Also, in an article in code project i read that if you do not change the
major and minor version and just change the build and revision number , the
application would pickup the latest version from GAC. I tried it but it did
not work  . Please let me know if this is true or if it works for you.
Cheers,
Sachin
"John Lee" wrote:
> Yes, when I move the <runtime> bindingRedirect into BTSSvc.exe.config and it
> worked!!! But mess around with this configuration file is kinda scary though
>
>
> Thanks Sachin!
>
> John
>
> "Sachin Surana" <SachinSurana@discussions.microsoft.com> wrote in message
> news:482BB7E6-5C0C-4307-AB06-1E04B12BF91E@microsoft.com...
>
>
>
|
|
|
|
|