Stopping ASP.NET 2.0 bulk compilation...

[James]

Hi,

I am migrating an enterprise application from ASP 3.0 with server-side
JScript to ASP.NET 2.0.

There are over 400 pages.

If I try to access one of the migrated .aspx pages, the aspnet_ws
process tries to compile all of the pages.

This times-out the initial page request to the browser.

What I would like is for just the page I am requesting to be compiled.

How can I configure ASP.NET 2.0 to do this please?

Thanks in advance for any help.

Best Wishes,
James

 

[S. Justin Gengo]

James,

I'd suggest a different route. With asp.net 2.0 you can build your entire
application as "pre-compiled" then no compilation on page request will be
necessary and your overall application will be much faster.

When you go to build your application for deployment use Build - Publish Web
site and uncheck "Allow this precompiled site to be updateable.

This article gives many more details:
http://www.odetocode.com/Articles/417.aspx


Regards,

--
S. Justin Gengo
Web Developer / Programmer

Free code library:
http://www.aboutfortunate.com

"Out of chaos comes order."
Nietzsche

 

[James]

I'd suggest a different route. With asp.net 2.0 you can build your entire
application as "pre-compiled" then no compilation on page request will be
necessary and your overall application will be much faster.

When you go to build your application for deployment use Build - Publish Web
site and uncheck "Allow this precompiled site to be updateable.

This article gives many more details:
http://www.odetocode.com/Articles/417.aspx

Thanks for your quick response, I shall follow your advice
for deployment time.


While testing and refactoring, I've found that this minimal
web.config file will do the trick:

<configuration>
<system.web>
<compilation batch="false"/>
</system.web>
</configuration>

Best Wishes,
James