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

[Robert Jordan]

Hi Dave,

On 05.02.2011 15:05, Dave Glick wrote:
>> 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.

I'm deploying using a Makefile and MS.NET's aspnet_compiler.exe.
Never used a Web Deployment addin.

> 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"/>

Same here.

> 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

Same here except for "WebAppDeploy.dll". I have only
Web Applications w/out App_Code folders. Maybe this makes the
difference.

> 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.

The placeholder *.as?x files are probably provided for
web servers that require these files to exist to be
able to route the request to the appropriate handler.

Maybe some older IIS version (6?) required this.

> 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...

I believe that the Web Deployment addin is simply deleting
theses files because current Web server versions do not
require them.

Try to create an empty Default.aspx (make it at least one
byte large just to be sure). If it works, then XSP is
the culprit because it is trying to access the file
physically. Please report a bug in this case.

Robert