>The reason I am asking was I am building an in-process .DLL for running inside MTS and IIS. Once the server starts getting called heavily, the only way to update the business-logic method code would be to down the whole web server.

Not true. MTS (and COM+ in Win2K) have functions that allow you to unload any package. You can even do it programmatically with MTS' COM interface. All this could be done from a project hook, so every time you compile, the package (or COM+ application) is stopped and the dll can be overwritten, and the package refreshed.

AFAIK, there is no way to keep MTS from trying to reload the package after it has been stopped (for the time that it is down, and you are trying to recmpile) so for servers that get pretty heavy traffic, you will have to shut the web service down, but this can also be done fairly easily programmatically, and if handled from a hook, the total downtime would be no more than a few seconds.

Either way, I think that placing your app's business code in memo fields looks neat from a distance, but would quickly grow to be a thorn in your side.