tag:blogger.com,1999:blog-7104252.post109786497110906278..comments2020-07-31T17:12:27.477-04:00Comments on Musings of a .Net Developer: Pre-compilation in ASP.NET v1.1.Net Geekhttp://www.blogger.com/profile/01302576643296966132noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-7104252.post-1111745899149812012005-03-25T05:18:00.000-05:002005-03-25T05:18:00.000-05:00Perhaps the System.Web.Handlers.BatchHandler is us...Perhaps the <I>System.Web.Handlers.BatchHandler</I> is used when the web.config<BR/><A HREF="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpgenref/html/gngrfcompilationsection.asp" REL="nofollow">\configuation<BR/>\system.web<BR/>\compilation<BR/>\debug, batchTimeout, maxBatchSize, maxBatchGeneratedFileSize</A> are set?<BR/><BR/>These settings control whether the ASP.NET engine compiles ASPX pages individually, or in 'batches'! IF debug="false":<BR/><A HREF="http://www.aspnetresources.com/articles/debug_code_in_production.aspx" REL="nofollow">when an ASP.NET file is requested for the first time the framework conducts a batch compilation <I>on that directory</I>. It compiles files in that directory only into a DLL. It does not traverse subfolders. You need to hit a page in every folder to have each folder batch compiled. This is an important point.</A><BR/>-- Sounds like what the BatchHandler is doing...<BR/><BR/>For a custom approach to pre-compilation, see <A HREF="http://jonijpn.jugem.cc/?eid=21" REL="nofollow">Joni Zhang's Precompile.axd HttpHandler</A> and/or <A HREF="http://www.users.bigpond.com/conceptdevelopment/.net/precompile/" REL="nofollow">my 'improvements'</A><BR/><BR/>HTHCraig Dunnhttps://www.blogger.com/profile/09377896535933926653noreply@blogger.com