|
Home > Archive > BizTalk Server General > October 2005 > Newbie ques. abt deployment BTS Orch and non-bts assemblies
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 |
Newbie ques. abt deployment BTS Orch and non-bts assemblies
|
|
| krakow007 2005-10-04, 5:53 pm |
| Hello,
Apologize if answered elsewhere, but did a search and could not find
the answers.
I have a few orchestrations that are dependent on some non-BTS
assemblies which are installed in the GAC.
Assuming that the non-BTS assemblies themselves are set to have fixed
version no.s (we have no need for co-existense of supporting
side-by-side versions) and are always uninstalled from the GAC before
re-installing the new "versions", my question is -
When deploying any changes to the non-BTS assemblies, can I just -
1.) Stop the biztalk ports, orchestrations and the instance of the BTS
server,
2.) Uninstall and re-install the changed non-BTS assemblies into the
GAC
3.) Restart the instance of the BTS server along with all the
applicable BTS components (orchestrations, ports etc)
Are the above steps enough to deploy changes to the non-BTS assemblies
or do I need to rebuild and redeploy the biztalk assemblies too along
with the above ?
Thanks in advance for your answers
| |
| carlos 2005-10-04, 5:53 pm |
|
hi krakow..
when you change the number version of one assembly and you had associated a
strong name, the relation between two assemblies is lost....
you have two options... one is to rebuild and redeploy your biztalk assembly
that reference the new non-bts assemblie... or the second option is use the
assemblyBinding section
(http://msdn.microsoft.com/library/d...ingredirect.asp)
and modify the BTSNTSvc.dll.config for redirect the previous assembly to new
assembly
is better to use the first option (rebuild) instead of modify the
..dll.config bts file...
"krakow007" wrote:
> Hello,
> Apologize if answered elsewhere, but did a search and could not find
> the answers.
> I have a few orchestrations that are dependent on some non-BTS
> assemblies which are installed in the GAC.
> Assuming that the non-BTS assemblies themselves are set to have fixed
> version no.s (we have no need for co-existense of supporting
> side-by-side versions) and are always uninstalled from the GAC before
> re-installing the new "versions", my question is -
> When deploying any changes to the non-BTS assemblies, can I just -
> 1.) Stop the biztalk ports, orchestrations and the instance of the BTS
> server,
> 2.) Uninstall and re-install the changed non-BTS assemblies into the
> GAC
> 3.) Restart the instance of the BTS server along with all the
> applicable BTS components (orchestrations, ports etc)
> Are the above steps enough to deploy changes to the non-BTS assemblies
> or do I need to rebuild and redeploy the biztalk assemblies too along
> with the above ?
> Thanks in advance for your answers
>
>
| |
| carlos 2005-10-04, 5:53 pm |
|
hi krakow..
when you change the number version of one assembly and you had associated a
strong name, the relation between two assemblies is lost....
you have two options... one is to rebuild and redeploy your biztalk assembly
that reference the new non-bts assembly... or the second option is use the
assemblyBinding section
(http://msdn.microsoft.com/library/d...ingredirect.asp)
and modify the BTSNTSvc.dll.config for redirect the previous assembly to new
assembly
is better to use the first option (rebuild) instead of modify the
..dll.config bts file...
"krakow007" wrote:
> Hello,
> Apologize if answered elsewhere, but did a search and could not find
> the answers.
> I have a few orchestrations that are dependent on some non-BTS
> assemblies which are installed in the GAC.
> Assuming that the non-BTS assemblies themselves are set to have fixed
> version no.s (we have no need for co-existense of supporting
> side-by-side versions) and are always uninstalled from the GAC before
> re-installing the new "versions", my question is -
> When deploying any changes to the non-BTS assemblies, can I just -
> 1.) Stop the biztalk ports, orchestrations and the instance of the BTS
> server,
> 2.) Uninstall and re-install the changed non-BTS assemblies into the
> GAC
> 3.) Restart the instance of the BTS server along with all the
> applicable BTS components (orchestrations, ports etc)
> Are the above steps enough to deploy changes to the non-BTS assemblies
> or do I need to rebuild and redeploy the biztalk assemblies too along
> with the above ?
> Thanks in advance for your answers
>
>
| |
| Jan Eliasen 2005-10-05, 7:48 am |
| On Tue, 4 Oct 2005 10:05:03 -0700, carlos
<carlos@discussions.microsoft.com> wrote:
>when you change the number version of one assembly and you had associated a
>strong name, the relation between two assemblies is lost....
>
>you have two options... one is to rebuild and redeploy your biztalk assembly
>that reference the new non-bts assembly... or the second option is use the
>assemblyBinding section
>(http://msdn.microsoft.com/library/d...ingredirect.asp)
>and modify the BTSNTSvc.dll.config for redirect the previous assembly to new
>assembly
>
>is better to use the first option (rebuild) instead of modify the
>.dll.config bts file...
Hi
The questioner said that the version numbers are fixed.
--
Jan Eliasen, representing himself and not the company he works for.
| |
| carlos 2005-10-05, 9:01 pm |
| thanks jan,
I read bad the post, sorry.... if the version number has fixed you don't
need to rebuild your biztalk solution... only if your non-bts assemblies had
change the number version or sn is necessary rebuild and redeploy your bts
solutions...
"Jan Eliasen" wrote:
> On Tue, 4 Oct 2005 10:05:03 -0700, carlos
> <carlos@discussions.microsoft.com> wrote:
>
> Hi
>
> The questioner said that the version numbers are fixed.
>
> --
> Jan Eliasen, representing himself and not the company he works for.
>
| |
| krakow007 2005-10-05, 9:01 pm |
| Thanks Carlos and Jan,
Like Jan mentioned, the version numbers are fixed. So I want to know
if, under these circumstances, I can just get away by deploying the
new non-biztalk assemblies in the GAC, bounce all the biztalk
components (hosts, ports, orchestrations etc) and have my
orchestrations recognize the new non-biztalk dlls.
Thanks again.
| |
| carlos 2005-10-05, 9:01 pm |
|
hi kra...
Excuse me... I read bad the post, sorry.... if the version number has fixed
you don't
need to rebuild your biztalk solution, may be you have to restart
bts-services to ensure the release of cache... only if your non-bts
assemblies had change the number version or sn is necessary rebuild and
redeploy your bts solutions...
"krakow007" wrote:
> Thanks Carlos and Jan,
> Like Jan mentioned, the version numbers are fixed. So I want to know
> if, under these circumstances, I can just get away by deploying the
> new non-biztalk assemblies in the GAC, bounce all the biztalk
> components (hosts, ports, orchestrations etc) and have my
> orchestrations recognize the new non-biztalk dlls.
>
> Thanks again.
>
>
|
|
|
|
|