Excellent. I think all of us career ASP .NET types has a function like this floating around in our utilities pile. =)

The System.Web.UI.Control class has a method called ResolveClientUrl() that does the same thing. Looking at the source code through Reflector shows its implementation to be much more complicated than yours. Plus it requires a Control instance. Here's my C# implementation of the same idea:

public static string ResolveRelativeUrl(string relativeUrl)

{

if (!relativeUrl.StartsWith("~/"))

return relativeUrl;

else

{

string currentApplicationPath = HttpContext.Current.Request.ApplicationPath;

string relativeUrlWithNoLeadingTildeSlash = relativeUrl.Remove(0, 2);

return currentApplicationPath + relativeUrlWithNoLeadingTildeSlash;

}

}

ResolveClientUrl is probably more complicated because it doesn't do the exactly same thing as what's posted here. I always just use ResolveUrl or ResolveClientUrl. They already exist in the framework and while you do need a Control instance, if you have the Page object handy then that'll do just fine. ResolveClientUrl will give you a relative path depending on what page you're on (i.e. "../../test/test.aspx"), while ResolveUrl will give you an absolute path from the root of the app (i.e. "/root/test/test.aspx").

I'm just bothered by doing the StartsWith twice for no reason. Here's the revised code: