Hello,

I'm working on the WebService example of the Biztalk's SDK.
I added an expression to call a .net component and added
some log like EventLog.Write("Start Expression").

When i modify this expression, i build the solution,
launch "cleanup" and "setup", unenlist and start the
orchestration.

After that, the old expression is still executed instead
of the modified one.

Have you got any idea ?

Thanks,
arno

[ Post a follow-up to this message ]

These are the steps I use:
1. Unenlist orchestrations (terminating running instances)
2. Remove pipeline and map references from ports
3. Undeploy assembly
4. Restart Biztalk Service
5. Deploy new assembly
6. Reference pipelines and maps in ports
7. Bind orchestrations
8. Enlist and start orchestrations

Step 4 can be done last but needs to be done.

Steps 1 and 8 can be done from Biztalk Explorer or Biztalk Administrator
Step 2 and Steps 5,6,7 can be done using a binding file and the deployment
wizard.

There are some useful looking tools available to automate this process, but
I have not yet tried them

Greg

"arno" <anonymous@discussions.microsoft.com> wrote in message
news:80ea01c4ce12$4ddb3000$a301280a@phx.gbl...
> Hello,
>
> I'm working on the WebService example of the Biztalk's SDK.
> I added an expression to call a .net component and added
> some log like EventLog.Write("Start Expression").
>
> When i modify this expression, i build the solution,
> launch "cleanup" and "setup", unenlist and start the
> orchestration.
>
> After that, the old expression is still executed instead
> of the modified one.
>
> Have you got any idea ?
>
> Thanks,
> arno

[ Post a follow-up to this message ]

Hi,

The NAnt Build tool is great for doing this, it takes an hour or so to get i
setup with a project the first time, but you save so much time after that.

This link is here:
http://www.traceofthought.net/Perma...00.
aspx

Regards,

Alan




"Greg Forsythe" wrote:

> These are the steps I use:
> 1. Unenlist orchestrations (terminating running instances)
> 2. Remove pipeline and map references from ports
> 3. Undeploy assembly
> 4. Restart Biztalk Service
> 5. Deploy new assembly
> 6. Reference pipelines and maps in ports
> 7. Bind orchestrations
> 8. Enlist and start orchestrations
>
> Step 4 can be done last but needs to be done.
>
> Steps 1 and 8 can be done from Biztalk Explorer or Biztalk Administrator
> Step 2 and Steps 5,6,7 can be done using a binding file and the deployment
> wizard.
>
> There are some useful looking tools available to automate this process, bu
t
> I have not yet tried them
>
> Greg
>
> "arno" <anonymous@discussions.microsoft.com> wrote in message
> news:80ea01c4ce12$4ddb3000$a301280a@phx.gbl... 
>
>
>

[ Post a follow-up to this message ]