Wrong question. Paths in a Web application are irrelevant to the application path. Relative URI addressing is based on the location of a current page. In other words, if your host page has some location, and you use the URI of the iframe content something as "frames/myFrame.html" (same as "./frames/myFrame.html"), it means the resource is taken from the sub-directory "frames" of the directory of your host page location.
But URIs like "file:E:\Shared-Files\..." you are trying to use are simply illegal in Web application. The HTTP server executes your application is a sandboxed environment, which allows you to access only the file system object under the site's root directory. So, the absolute directory can be only calculated based on this root directory. In ASP.NET, it can be done based on
MapPath
:
http://msdn.microsoft.com/en-us/library/system.web.httpserverutility.mappath.aspx[
^].
As to URLs, the should either be built based on the site's root using the "http://" or "https://" URI schema, or, more often, should be relative.
—SA