Page.ResolveUrl（）在VS2010 Dev Server上不起作用

Question

I'm trying to use an existing, old, ASP.Net web application that will serve as the main UI for our project. The web application employs MANY user controls, with a lot of:

<element attribute='<%=Page.ResolveUrl("~/path/to/resource")' ...

I have a problem, however. If the application is deployed to IIS, these calls to Page.ResolveUrl() work fine. But if I try to run this application in Visual Studio Development Server, it does not resolve any URLs (ie, no styles applied, no images rendered, etc.)

// If deployed in IIS, the style tag renders like this (and works):
<link href="/adminconsole/styles/styles.css" ...

// On the VS Dev Server:
<link href="/styles/styles.css" ...

What I want, is for these calls to "just work" no matter if the application is deployed to IIS, or is running on the Visual Studio Development Server.

Some pertinent info:

The web app does not use a master page. It includes the header as a user control :(

Answer 1

The VS Dev web server is usually having only one site and accessing on localhost with a certain port number. Check project properties in web tab and see if you can change that Url to have a site name like you have in IIS. If not possible and if you are not willing to change the code make your developers to use local IIS or IIS express instead of that little VS toy.

In my experience is anyway much better to develop and test on IIS because you work in a more similar to production environment and if any, you discover issues earlier so have more time to react not last night before go live.

Answer 2

I had to do something like this very recently but instead of using <%=ResolveURL("~/path/to/file")%> I used <%=ResolveURL("relative/path/to/file")%> try that to see if that works. It worked for me.

I also think that testing/debugging on local IIS is definitely better. Remember, Cassini (the toy web server that ships with VS) runs under the developer's credentials so permissions to the local file system are very different compared to running your website on IIS directly.