HttpRequest.CurrentExecutionFilePath Property
Gets the virtual path of the current request.
Assembly: System.Web (in System.Web.dll)
CurrentExecutionFilePath returns the file path to the currently executing page handler. For redirect scenarios using Execute and Transfer methods this means that the CurrentExecutionFilePath property returns the path to the page redirected to (child page). However, when the client is redirected to another page, the FilePath property returns the path to the original page.
The following code example uses the HtmlEncode method to HTML-encode the value of the CurrentExecutionFilePath property and the WriteLine method to write the encoded value to the file. This code example is part of a larger example provided for the HttpRequest class.
// Write request information to the file with HTML encoding.
sw.WriteLine(Server.HtmlEncode(DateTime.Now.ToString()));
sw.WriteLine(Server.HtmlEncode(Request.CurrentExecutionFilePath));
sw.WriteLine(Server.HtmlEncode(Request.ApplicationPath));
sw.WriteLine(Server.HtmlEncode(Request.FilePath));
sw.WriteLine(Server.HtmlEncode(Request.Path));
Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows XP SP2 x64 Edition, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2
The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.
sw.WriteLine(Server.HtmlEncode(Request.CurrentExecutionFilePath));
tells me nothing about the behavior of the method other than it returns a string!
Whenever "examples" like this are included they should *always* show the expected output somewhere.
I appreciate that this snippet is from a larger "example" but that too is useless unless download, compile and and run the code, which all takes time.
Please stop using "examples" like this - it just makes me so mad.
- 9/5/2011
- chrisfewtrell
- 9/5/2011
- Thomas Lee
- 5/25/2010
- Erik Reitan
