[Mono-aspnet-list] Bug With Default Index Files (MonoServerDefaultIndexFiles) and Pre-compiled Sites with Xsp2

Dave Glick dglick at dracorp.com
Sat Feb 5 09:05:58 EST 2011

> When I precompile my sites with MS.NET 3.5, all *.as?x files are kept in place with their content replaced with:
> "This is a marker file generated by the precompilation tool, and should not be deleted!"
> So they are actually physically existent, additionally to their precompiled form in the "bin" directory.
> Please explain how and with which tool/.NET version you're precompiling your site.

Very interesting, there must be multiple ways to handle precompiled sites. I'm using Visual Studio 2008 with the official Web Deployment Projects addin in order to automate the build and deployment process. After a build, I only have two files in my root: PrecompiledApp.config and web.config. The PrecompiledApp.config file has the following short content:

<precompiledApp version="2" updatable="false"/>

In my /bin directory I have WebApp.dll (the name of my web application project), WebAppDeploy.dll (the name of my web deployment project), and a couple pagename.aspx.randomstuff.compiled files with the content I mentioned earlier. That's it - no mirror of the precompiled files with placeholder text at the physical location. This all works great in IIS and also in Xsp, except for the default index feature.

This makes me think that the web framework must be able to handle a couple different cases when it comes to precompiled sites, so my original suggestion probably wouldn't work. In your scenario do you still end up with the *.compiled files in the /bin directory? There must be some way to query the framework for a list of cached precompiled page virtual paths...


More information about the Mono-aspnet-list mailing list