Forum Version: 1.9.3 RC2
Host OS: Windows 7 Build 7077
.NET Version: .NET 3.5
Errors: "The virtual path '/forum/pages/forum.ascx' maps to another application, which is not allowed."
URL: http://localhost/forum
Installation Issues: No Installation Issues

Ok I can upload my code for my website exactly as it is to windows server 2003 x64 and it runs fine. I used to have this problem on the server but I just ran IIS Manager and configured the /forum/ directory as an application. However, I have no known "IIS" manager using the ASP.NET Development Server, nor do I know how to configure it to make this change, or if I can edit a local file to make this change. Any suggestions? Thanks.

Please refer to installation manual which says:

STEP 5. (OPTIONAL) MODIFY "app.config" FILE:

By default YAF is designed to be installed at the root application on any
IIS web server. If you want YAF to be installed off of the main root, you need
to modify the root key. Make sure the files in the /bin directory of the YAF zip
file are copied to /bin directory on the root of your web server.

Then open up "app.config" and uncomment the "root" key. Enter the value as the
directory to your forum.

Example: If you have install the forum in the directory "/forum/yaf/"
you will need to add key with name "root" and value "/forum/yaf/"
to app.config.

Also, in "app.config" you can modify the BoardID to use the board you want.
If you only have one board or don't know what this is, leave it alone.

I had to already make this modification to get it to work on the windows server 2003 site. It works on an IIS server, but I'm having trouble running it in visual studio 2008, as I get this error. My app.config has this change, however it still gives the error...

k I've never seen that error using the ASP.NET Development Server; i would also highly advise against developing with it; since it behaves very very differently to IIS which can lead to an absolute nightmare when transferring to IIS (been there 😞 )

You can get Visual Studio to publish to IIS, and not run its web server. Whether this is wholly working in Windows 7 I have no idea.

---

k I've never seen that error using the ASP.NET Development Server; i would also highly advise against developing with it; since it behaves very very differently to IIS which can lead to an absolute nightmare when transferring to IIS (been there 😞 )

You can get Visual Studio to publish to IIS, and not run its web server. Whether this is wholly working in Windows 7 I have no idea.

On windows server 2008 remote debugging is supposedly easy, but for some reason I can't seem to get it to run with windows server 2003. Local debugging would be easier for my case honestly, but I have no idea how to configure ASP.NET Development server....