| Don Keller 2005-04-27, 5:52 pm |
| Thanks for the helpful information. I wasn't aware that you could perform
the undeploy/re-deploy steps through BT Explorer. I just tried that and it
is much easier than using a separate tool, especially with repeated,
iterative changes during development. After using that approach my
orchestration changes still didn't go into effect. I did finally restart the
host however and then they did.
Thanks again,
Don
"Mike" wrote:
[vbcol=seagreen]
> Don,
>
> Deploying is time-consuming and I haven't got the art of it figured out just
> yet. However, I can offer a few suggestions that seem to work for me:
>
> 1) I create batch files to deploy directly into the GAC. These changes
> "sometimes" take affect and sometimes do not. I haven't quite figured out
> the changes that take affect w/o requiring a new deployment vs. the ones that
> don't, but usually try this first, especially when I am making simple changes
> to the orch.
>
> 2) Undeploy and Re-deploy directly from Visual Studio.NET if this is an
> option for you. It saves the repeated wizard steps for one binary at a time.
> Within Visual Studio.NET, go to View | BizTalk Explorer. You can unenlist
> your orchs and then undeploy your assemblies. Then, go to "Build | Deploy
> Solution". This will do for you what you are doing through the wizard right
> now and save a lot of time.
>
> 3) Things to get cached. When I re-deploy via the method in step 2 above I
> don't have do stop/restart anything. You can stop/restart BizTalk if you
> keep doing it the way that you described and it should help.
>
> 4) I am not an expert at this either and am in an isolated island and have
> suffered the same way you are. These newsgroups have been a great help to me
> and if someone has additional info and/or corrections to my post then please
> offer any advice that you may have!
>
> Regards,
>
> Michael
>
>
> "Don Keller" wrote:
>
|