aspx pages are compiled into temporary assemblies, which are stored on the
file system, in the ASP.NET Temporary Files folder.
So it's unlikely whatever extra effort you are referring to is going to buy
you much. Once the temp assembly is compiled, it would be just as fast as
what you are suggesting.
Peter
<te***@yahoo.com> wrote in message
news:11**********************@g49g2000cwa.googlegr oups.com...
As far as I know, aspx pages are compiled and stored in the server's
memory the first time it's used. Would it make much difference if I
dump most of the code into a dll and have the page called that dll,
since both are already compiled?