I am actually looking to compile the aspx or the ascx file into a DLL and
then having the application dynamically create the controls that are
specified in these files when the stored aspx/ascx file is actually being
requested. (I wonder if there exist a technique similar to that of storing
images into the DLL and then dynamically retrieving the images as the web
client requests it.).
The reasoning behind doing things this way is to prevent the user from
modifying/tampering with the aspx/ascx files.
ASP.NET in Whidbey will fully support that model; however it won't be
available for production use for a while.
In the meantime, if you specify Debug='true' in the @Page directive for
the .aspx page, the parsed C# (or VB.NET) source remains available in
the temporary directory. You could pull that source file out of there,
and compile it yourself.
I'm sure there's a better way of doing this, probably by using some
undocumented classes in the framework, but this might be a n easy way
for you to experiment while you're figuring out a better method.