BTW, compiled code is not by definition faster than interpreted code. The code bloat created by traditional compiled dlls can actually make them slower than interpreted code. The magic of the .Net runtime is that it will only compile the stuff it needs (unless you ngen your assembly of course).
-- Henkk ----- Original Message ----- From: "Thomas Tomiczek" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, April 18, 2002 5:20 PM Subject: Re: [DOTNET] how asp.net handles aspx page? > They ARE also compiled into DLL's and there is a cache directory > somwhere. > > > Regards > > Thomas Tomiczek > THONA Consulting Ltd. > (Microsoft MVP C#/.NET) > > > > -----Original Message----- > From: ChongQing Xiao [mailto:[EMAIL PROTECTED]] > Sent: Donnerstag, 18. April 2002 16:37 > To: [EMAIL PROTECTED] > Subject: [DOTNET] how asp.net handles aspx page? > > > Hi, > > For ASP.NET, it mentioned it use compiled code so it can run faster than > asp. Suppose I have a A.Aspx and A.Aspx.cs (code behind), I know the > A.Aspx.cs is compiled to an assembly before executed, but I wonder if > ASP.NET precompiles A.Aspx before executed it, if yes, will the compiled > code being cached? > > thanks > chong > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, > or subscribe to other DevelopMentor lists at http://discuss.develop.com. > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
