| Author |
Redeploying assemply in use from elsewhere -
|
|
| Paw Pedersen 2005-01-14, 7:50 am |
| When trying to deploy a Biztalk project (is configured with "yes" to
redeploy) that has already been deployed, I get a dependence error because
some other projects or ports are using items from this project.
Is it possible to somehow force this redeploy?
If not, is it possible to get a list of assemplies and ports that depend on
this assemply?
This is really a big problem in Biztalk so I hope there is a solution for
easier deployment. And NOT by incrementing the version no, because this
gives me a lot of other problems.
Regards Paw
| |
| Danny Buysse 2005-01-14, 5:49 pm |
| Have a look at Scott Colestock's BizTalk 2004 “Deploy with NAnt” Template
Sample at
http://www.traceofthought.net/Perma...afc2d89084.aspx
Danny Buysse
http://dannybuysse.blogspot.com/
"Paw Pedersen" wrote:
> When trying to deploy a Biztalk project (is configured with "yes" to
> redeploy) that has already been deployed, I get a dependence error because
> some other projects or ports are using items from this project.
> Is it possible to somehow force this redeploy?
> If not, is it possible to get a list of assemplies and ports that depend on
> this assemply?
> This is really a big problem in Biztalk so I hope there is a solution for
> easier deployment. And NOT by incrementing the version no, because this
> gives me a lot of other problems.
>
> Regards Paw
>
>
>
| |
|
|
| Ben Cuttriss 2005-01-14, 5:49 pm |
| Paw,
What do you need to do - you know that you can overwrite the orchestration
dll in the GAC - simply drag the dll into the assembly folder (Start -- run
-- Assembly).
Then just restart the Biztalk application service.
HTH
Ben
"Paw Pedersen" wrote:
> When trying to deploy a Biztalk project (is configured with "yes" to
> redeploy) that has already been deployed, I get a dependence error because
> some other projects or ports are using items from this project.
> Is it possible to somehow force this redeploy?
> If not, is it possible to get a list of assemplies and ports that depend on
> this assemply?
> This is really a big problem in Biztalk so I hope there is a solution for
> easier deployment. And NOT by incrementing the version no, because this
> gives me a lot of other problems.
>
> Regards Paw
>
>
>
| |
| Paw Pedersen 2005-01-17, 7:47 am |
| Thank you Ben
I will try this the next time I have the problem.
But will this also work if for instance the only thing I change in a project
is to promote an attribut in a schema to be able to reference it from the
port setup?
Regards Paw
"Ben Cuttriss" <BenCuttriss@discussions.microsoft.com> wrote in message
news:945710DE-D2EC-424E-88AF-051886BA25DE@microsoft.com...
> Paw,
>
> What do you need to do - you know that you can overwrite the orchestration
> dll in the GAC - simply drag the dll into the assembly folder (Start --
run[vbcol=seagreen]
> -- Assembly).
>
> Then just restart the Biztalk application service.
>
> HTH
> Ben
>
> "Paw Pedersen" wrote:
>
because[vbcol=seagreen]
on[vbcol=seagreen]
for[vbcol=seagreen]
| |
| Paw Pedersen 2005-01-17, 7:47 am |
| Thank you Jon,
I have downloaded your tool, and will try it out if Ben Cuttriss's approach
doesn't work.
Regards Paw
"Jon Flanders" <jfland@develop.com> wrote in message
news:#9ZPVol#EHA.1524@TK2MSFTNGP09.phx.gbl...
> That is the whole reason I wrote my snapshot tool
>
http://staff.develop.com/jfland/Per...7e-034102c3f390
> it detects the dependencies and undeploys in the necessary order. Then
you
> can reploy the whole "application" all at once. They way I use it during
> builds is to undeploy, copy the newly built assembly into the
"application"
> directoryI make and the tool again with the "restore" command.
>
> --
> Jon Flanders [DevelopMentor]
> http://staff.develop.com/jfland/
> http://www.develop.com/courses/biztalk
> "Danny Buysse" <DannyBuysse@discussions.microsoft.com> wrote in message
> news:EC380A08-AF8C-4B9F-AEDC-512DBE6E8FCE@microsoft.com...
Template[vbcol=seagreen]
>
http://www.traceofthought.net/Perma...afc2d89084.aspx
> because
depend[vbcol=seagreen]
> on
> for
this[vbcol=seagreen]
>
>
| |
| Ben Cuttriss 2005-01-25, 5:50 pm |
| Paw,
I think you'll get into trouble doing this. The problem (as far as I
understand it) is that the assembly does not handle the promoting of the
attributes - it is the process of installing the assembly (schemas and all)
that handles this.
Sorry - don't think so.
"Paw Pedersen" wrote:
> Thank you Ben
> I will try this the next time I have the problem.
> But will this also work if for instance the only thing I change in a project
> is to promote an attribut in a schema to be able to reference it from the
> port setup?
>
> Regards Paw
>
> "Ben Cuttriss" <BenCuttriss@discussions.microsoft.com> wrote in message
> news:945710DE-D2EC-424E-88AF-051886BA25DE@microsoft.com...
> run
> because
> on
> for
>
>
>
|
|
|
|