UrlParser.Parse and HttpRequest.AppRelativeCurrentExecutionFilePath

Topics: Web Client Software Factory
Nov 22, 2006 at 11:21 AM
Why use UrlParser.Parse instead of HttpRequest.AppRelativeCurrentExecutionFilePath?
Jan 3, 2007 at 2:24 PM
Still no clue for this.
Jan 5, 2007 at 2:20 AM
Looks like it was done in order to enable unit testing outside the IIS environment. But, after looking at the test, we decided that the test (and the method) weren't adding enough value. So, we replaced UrlParser.Parse with HttpRequest.AppRelativeCurrentExecutionFilePath. Of course, removing the Parse method from a class named UrlParser changes its responsibility. So, we changed the name of that class to HttpRequestHelper.
Jan 8, 2007 at 12:43 AM
It's still used in the current version of the PageFlowHttpModule.
Jan 8, 2007 at 4:31 AM
Check out today's drop. The new code is in it.