Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Managing url paths can be a real pain in ASP.NET. AbsolutePath vs RelativePath vs etc. drives me crazy. I find that many solutions require the user to edit web.config element to include the correct subfolder path; ex.
Website Root: http://www.domain.com Web.config setting: /
Website Root: http://www.domain.com/blog web.config setting: /blog/
Is there a way to properly handle this without having to make changes to the web.config?
You could use Request.ApplicationPath. A reference of usage is here.
This way your images folder, for example, will be Request.ApplicationPath + ‘/images/’;