I have an application that is running in a sub-directory under Umbraco. I've configured my web.config appropriately and everything runs, however, the application references HttpContext.Current.Profile.UserName and for some reason, under IIS6, the HttpContext.Current.Profile object is null. Same application, same web configs (yes, I know the system.web and server.web sections are different, but mine match) and it works fine under IIS7.
To further test, I create a simple 1 page application that outputs HttpContext.Current.Profile.UserName to a label and confirmed that as a standalone application, under IIS6, it works correctly. As soon as I move it to a sub-directory of Umbraco, and set it as an application, it throws an error because the Profile object is null.
Anyone heard of this behavior? Any suggestions on where to continue digging (I've been at it for 2 days now).
For anyone else that ever comes across a similar issue:
Turns out the problem was related to the HTTPHandlers section of the Web.config. I had removed the Umbraco HTTPHandlers and added a which apparently cleared something that was needed for profiles. Also, the trick to use:
HttpContext.Current.Profile in sub-application
I have an application that is running in a sub-directory under Umbraco. I've configured my web.config appropriately and everything runs, however, the application references HttpContext.Current.Profile.UserName and for some reason, under IIS6, the HttpContext.Current.Profile object is null. Same application, same web configs (yes, I know the system.web and server.web sections are different, but mine match) and it works fine under IIS7.
To further test, I create a simple 1 page application that outputs HttpContext.Current.Profile.UserName to a label and confirmed that as a standalone application, under IIS6, it works correctly. As soon as I move it to a sub-directory of Umbraco, and set it as an application, it throws an error because the Profile object is null.
Anyone heard of this behavior? Any suggestions on where to continue digging (I've been at it for 2 days now).
Thanks!
For anyone else that ever comes across a similar issue:
Turns out the problem was related to the HTTPHandlers section of the Web.config. I had removed the Umbraco HTTPHandlers and added a which apparently cleared something that was needed for profiles. Also, the trick to use:
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.