I have a web application project in VS 2005. I want to have the following directory structure for the output assemblies of my application.

    \---H
        |   H.csproj
        |   H.csproj.user
        |   Service1.asmx
        |   Service1.asmx.cs
        |   Web.config
        |
        +---bin
            |
            +---Debug
            |           H.dll
            |           Service1.asmx
            |           Service1.asmx.cs
            |           Web.config
            |           H.pdb
            |
            \---Release
                        H.dll
                        Service1.asmx
                        Service1.asmx.cs
                        Web.config
           
However, I get a run-time error from ASP.NET (hosted by Visual Studio) because it expects my assemblies to be in the bin folder. I want to retain this directory structure and still run my application from within Visual Studio. How can I do this? i.e.,

• How can I ensure that everything that is requried by application to run exists in the bin\Debug and bin\Release folders?
• How can I tell VS to use bin\Debug or bin\Release as the virtual folder for running my application depending on the active configuration when I hit F5 in VS?
  

Essentially, I want to have a directory structure for web-applications that is similar to what I would for any other type of application (winApps, ConsoleApps etc.)

I would really appreciate any help. Thanks.

You can tell the runtime where to probe using the configuration like this:

<configuration>
	<runtime>
		<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
			<probing privatePath="bin;bin\Release"/>
		</assemblyBinding>
	</runtime>
</configuration>

For mor information see this page:
http://msdn2.microsoft.com/en-us/library/4191fzwb.aspx

Berehem:

How can I tell VS to use bin\Debug or bin\Release as the virtual folder for running my application depending on the active configuration when I hit F5 in VS?

That's possible, but it would require defining the paths programmically with the AppDomain and not use the config file.

---