<div>
Why not just visit the page yourself after updating so the user doesn't experience the wait?
</div>


<div>
Actually, we have hosted our web application at so many locations(on different customer's servers as well as in our hosting environment), so it is bit lengthy to visit each and every website after updating. And this slowness issue after update is not specific to first login page only but it is happening for all inner pages(directory wise) also first time.
</div>


<div>
<div class="content wysiwyg-content">
How can we avoid recompilation of ASP.NET webapplication when new DLL file(under bin folder) updated? If recompilation is unavoided then can it be automated? We are attempting to avoid disadvantage of recompilation which is slow response of web application when user runs it first time after recompilation.
</div>
</div>


How can we avoid recompilation of ASP.NET webapplication when new DLL file(under bin folder) updated? If recompilation is unavoided then can it be automated? We are attempting to avoid disadvantage of recompilation which is slow response of web application when user runs it first time after recompilation.

Slow response of web application first time after recompilation

Web applications are systems that run in browsers that perform functions normally associated with other client-based programs. One of the most commonly used web applications is email; instead of downloading individual emails to a local machine, the data is shown through a website. Other examples of web applications are collaborative systems like a wiki or an online game.