| Matt Milner 2004-06-20, 11:09 pm |
| You were probably running into a problem where the biztalk service was
holding on to the old copy of your assembly(orchestration). You need to
stop and start the biztalk service when redeploying an assembly with the
same version.
Matt
"Neal Walters" <NealWalters@discussions.microsoft.com> wrote in message
news:3D207B88-0BE3-4C93-B858-8AE88AF8402C@microsoft.com...
> I just made a separate thread/topic about increasing the major/minor
version number.
> Apparently this is getting me past this problem. So my guess is that we
should always bump up the version number for each deploy? Something
somewhere is not getting cleared out? Maybe the cache? I know in class,
there are many times where we have to start/stop the Host. Would changing
cache refresh to 0 or 1 be advisable on the development system?[vbcol=seagreen]
>
> Neal
>
>
> "Neal Walters" wrote:
>
different from yesterday), but with just as strange results:[vbcol=seagreen]
xmlns:ns0='http://EasyPOCorrelation.POConfirmation'><PONum>PONum_0</PONum><C
onfirmationDate>1999-05-31T13:20:00.000-05:00</ConfirmationDate><Confirmatio
nAmount>10.4</ConfirmationAmount></ns0:POConfirmation>");[vbcol=seagreen]
xmlns:ns0="http://EasyPOCorrelation.POConfirmation">[vbcol=seagreen]
have been ignored. The PONum in the output file has a value of "PONum_0"
instead of "override".[vbcol=seagreen]
|