It would be nice to have a way to provide the .aspx file via a stream from a
resource or some other source other than a file. That way we can create a
full library without the aspx stubs.
The solution I have now is to create a derived class from the pagehandler
class register it in the web.config file for the individual aspx page that is
in the resource. Create the file during runtime and delete it after it is
compiled (not decided if I want to delete the file).
Any issues using this approach?
KN
"Bruce Barker" wrote:
only javascript.net supports in memory compilation, the rest of the
compilers need a disk file. the in memory inteface to the other compilers
just writes the code to disk first.
-- bruce (sqlwork.com)
"KN" <KN@discussions.microsoft.com> wrote in message
news:44**********************************@microsof t.com... Hello,
Is it possible to provide the .aspx mark up to the buildmanager from a
resource for compilation and load it whithout having the .aspx file in the
virtual folder?
Since, the registered HTTP module is being executed before the .aspx page
is
compiled I was thinking it should be possible, but I can't seem to find a
way.
I was able to create the .aspx file physically using the
System.IO.Streamwriter and it worked fine. But is it possible to do it
without creating the file?
KN