The first time a site is hit IIS must load the asp.net worker process
and basically start up the .NET runtime. That takes a little bit of
time and is very noticeable on first hit.
You can use some outisde process like a scheduled task to force a load
when the computer starts up by requesting any random url within your
application, but ASP.NET will shut down the application based on
inactivity soon thereafter.
One thing I've done with some success is use a plain HTML file as the
first page and have that reference an aspx file (for an image or
something unimportant). The HTML file gets delivered quickly and the
referenced aspx file forces ASP.NET to load. You can have your app
generate the start page HTML file so it is not truely static. May not
work in all situations, but does in some.
HTH,
Sam
------------------------------------------------------------
We're hiring! B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.
On Thu, 20 Sep 2007 11:27:22 +0800, "Jason Huang"
<Ja************@hotmail.comwrote:
>Hi,
I tested my ASPNet web application and then found it takes a long time to
start at the first time.
So I surfed the web and found using aspnet_compile method.
When I execute the aspnet_compile -v /MyWeb, the compilation is OK and
returns no error.
But I found the speed didn't get promoted much, it still took long time to
open the application at the first time.
Would someone give me some advice?
Thanks for help.
Jason
