What's the idea behind changing the HTML in a htm-file when it gets deployed? The case where the image of the calendar control disappears after deploying it has been discussed here already, but now I noticed that a HTML-entity got replaced by a '?' (question mark) after deploying a file.
Why is deploy modifying HTML?

We are now leaning to not using deploy any more, but to use our version-control software (Mercurial) for that instead. Is there anything that deploy does that we should be aware of in that case? We don't use anything fancy like starting objects (a deploy feature).

This message has been edited. Last edited by: Kerry,

Deploy should not make any change to html files. That said, the deploy process isn't a must-have for anything short of WF Maintain files which are compiled during deploy. If you have an alternative method for deploying html files and the like, I'd use it and keep the Deploy feature of WF as light and simple as possible.

J.

Thanks for the confirmation.

quote:

Deploy should not make any change to html files

But it does. It checks the html source looking for references to the webserver from which it is being deployed. It will change those references to indicate the webserver that it is being deployed to.

Otherwise I agree with John. I normally do not use deploy, not even for maintain ... just copying from one server to the other works just as fine, provided the pathing on both servers is the same.

quote:
Deploy should not make any change to html files

But it does. It checks the html source looking for references to the webserver from which it is being deployed. It will change those references to indicate the webserver that it is being deployed to.

..... I spent a week week working with IBI tech support trying to get deploy to make the changes (WF7611). In the end discovered that deploy would only work when the name of the source and target directories is the same.

quote:

spent a week week working with IBI tech support trying to get deploy to make the changes (WF7611). In the end discovered that deploy would only work when the name of the source and target directories is the same.

Thatz an useful George... Thanks..