Bug 5616 - Disabling ASP.net application Bin shadow copy not working when using a virtual directory.
Summary: Disabling ASP.net application Bin shadow copy not working when using a virtua...
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System.Web (show other bugs)
Version: 2.10.x
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-06-12 09:45 UTC by rlauze
Modified: 2012-06-12 09:45 UTC (History)
1 user (show)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Hello world web service solution. (3.65 KB, application/x-zip-compressed)
2012-06-12 09:45 UTC, rlauze
Details

Description rlauze 2012-06-12 09:45:14 UTC
Created attachment 2041 [details]
Hello world web service solution.

When I use the settings <hostingEnvironment shadowCopyBinAssemblies="false"/> in the web.config file and use a virtual directory with the web server, the binaries are still copied to the ASP.Net Temporary Files directoryr. If I don't use the virtual directory, the binaries are not copied.

Steps to reproduce :

1- Make sure that the ASP.Net Temporary Files directory is empty to see the directory creation. In Windows, it's in %windir%\<currentuser>\AppData\Local\Temp\<username>-temp-aspnet\, in Linux /tmp/<webserver_username>-temp-aspnet

2- Compile the web service, the web.config file already has the right setting for shadowCopyBinAssemblies.

3- Start xsp web server with a virtual directory in the project root directory, xsp2 --applications /test:.

4- Connect to the web server and you'll see the dll copied in the ASP.Net Temporary Files directory.

5- To see the correct behavior, clean the ASP.Net Temporary Files directory. Start xsp without a virtual directory and connect to the web server. The binary is not copied.

Mono 2.10.8.1 x86 (Debian 2.10.8.1-1~dhx1~lucid1) Ubuntu lucid 10.04.4 LTS
Mono 2.10.8   x86 (tarball) Windows Vista

Not seen with Microsoft .Net.

Reproduced also with Linux.

Note You need to log in before you can comment on or make changes to this bug.