Application in asp.net slows down when a file is changed

You have two types of deployment models.

First is what we call a asp.net web site,
and then second, is what we call a asp.net web site application.

They sound the same – but they are not.

So, while most perfer using a "application"? The ONE down side is that you have to re-publish the WHOLE site if you say change some code behind. This is good, and bad. The good part is that your code is re-compiled BEFORE you publish. (and in fact, you might even want to re-name "app_code", since that does re-compile by the web site.

However, for the most part a web applcation is "harder" to make a small update, since when you publish, you have to re-publish the whole site. But, the good part is that all code tends to be compiled down to ONE .dll. In effect the the site is pre-compiled before publishing. And with a applciaton, then you can add/change and do more things. In effect, the web site "applcation" allows you to do things like create say a custom logon provider. In most cases, this means the WHOLE site is under your developer control. It also means that code behind (source code) is NOT pushed up to the site.

Then you have what is called a asp.net web site. This allows you to say modify the code (code behind) of one page and then push that one page (and code) up to the site. The web site will thus re-compile that one page. You will note the "delay" that you experiance – but it ONLY occures the first time that page is published.

So, for a "application", you will in Visual Studio open up the project (and a sln file) is used.

For a web site, you from Visual Studio go open->web site.

I hands down prefer web applications, but they are MUCH harder to deploy a small change, since as noted, you have to re-publish the whole site.

However, the two different choices would thus explain the "difference" and as to why the other site don’t experience the delay as much as you are. However, usually on first load – there can be a one time delay after a re-publish. And this quite much means the site is down for this time to re-publish.

Also, do keep in mind that if you do modify some files (such as web config), then this WILL cause the app-pool to re-start. (and if you not using sql server sessions, but in-memory sessions – they get blown out when you do this).

It also somewhat possible that the server with one user has more memory, more CPU and a much lighter load – so the reduced delay after making changes might well be the light load on that server.

However, the above two different publishing models and types of asp.net sites would be the first thing or at least the first issue to be aware of.