Hello!



Is there a way to prevent an ASP+ page to actually write the compiled

version to disk (in the /codegen directory)?! I've found when developing and

testing you get a lot of files in that directory. They're cached in memory

so I'd rather like to keep them in memory.



I am aware, that having rebooted, the webserver will have to spend time

compiling each successive ASP+ page from that point.



Does that sound like a good idea, or should I just ignore the growing

directory? When sitting 10 developers on the same site I recon that

directory would become really big!



with regards

anders lundholm · lundholm@s...

the sphereworx / monoliner experience

--

I think Beta 1 will be better on cleaning up the codegen directory when

the ASP+ engine compile a new version of a file.



In Beta 1 the codegen directory is not located under the app root.

It will be separated from your application.



I don't think you should be worried about this now, wait and see how this

is managed in Beta 1.



/Fredrik Normen