Last post Jun 02, 2015 01:41 PM by sks81
Jun 01, 2015 06:33 PM|sks81|LINK
After .Net Framework security update kb3037581, Context.Request.AppRelativeCurrentExecutionFilePath is giving encoded path like"~/Content/Setup%25252520and%25252520Monitoring/Parameter%25252520Maintenance/Parameter.aspx",
if we uninstall this update Context.Request.AppRelativeCurrentExecutionFilePath gives"~/Content/Setup Monitoring/Parameter
Maintenance/Parameter.aspx",which is what we are expecting.
We are using .Net Framework 4.5.1 with Windows 7 enterprise and Visual studio 2012.
Any one ran into similar kind of issue after .Net Framework kb3037581 security update.
Jun 02, 2015 07:07 AM|Weibo Zhang|LINK
I have found you post
a similar issue and I have had a basic understanding of your situation. I suggest that you could change your codes to make sure the path has no blank spaces. As we known, the programming specification requires a files path without spaces. The file path
which contains blank spaces may cause many weird exceptions in different environments.
If you couldn’t change the codes, I think you could communicate with your Enterprise Domain Control Manager to stop this patch updating on your server.
Jun 02, 2015 01:41 PM|sks81|LINK
thank you Weibo Zhang. As a short term we are uninstalling this update but as permanent fix we will remove blanks.