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.
I have an application in which HttpRuntime.AppDomainAppPath returns the correct path with the wrong casing.
I am then trying to use this in a String.Replace and it does not find the path in the filename due to casing.
I am aware that I can use Regex.Replace but would prefer not to.
I have this problem only on the production machine even though the folder in question has the same casing in dev.
I have just noticed that Server.MapPath also returns the wrong casing.
Any ideas?
Apparently the problem originated in the site directory being specified with the wrong casing in IIS. Merely changing the home directory does not help the problem as these values are already set in the metabase and apparently since windows in not case sensitive it does not fix the metabase when you fix it in the GUI.
I ended up removing the site and adding it again since it is not in use yet. I probably could have changed the directory name completely and changed the location in the GUI just as effectively.