HttpContext.Current.Request.ApplicationPath for website

Question

we had a web application deployed under virtual directory. Now we want to move it to it's own website for SSL configuration.

However, there are lots of HttpContext.Current.Request.ApplicationPath as a result the application is not working as expected.

Could anyone please help me with what's the alternative to HttpContext.Current.Request.ApplicationPath to find root of website?

On virtual directory setup it gives correct path to images whereas on website it just gives

http://images

which is not good.

Thanks heaps.

have you tried `Request.AppRelativeCurrentExecutionFilePath` or `ResolveClientUrl`? — Gary.S, Feb 28 '12 at 06:04

score 0 · Accepted Answer · answered Feb 28 '12 at 07:21

0

You can try this one

HttpRuntime.AppDomainAppPath

and alternative

HttpContext.Current.Request.PhysicalApplicationPath

answered Feb 28 '12 at 07:21

Aristos

1 Answers1