Try adding the following to your system. WebServer> ) Edit (in response to your comment): Sorry, I don't know much about how RoleManager depends on other modules. You can view the default IIS configuration by looking at c:\Windows\System32\inetsrv\config\applicationHost.
Config (at least, that's the past on my Windows Vista machine) to see the order in which modules are loaded (note the use of managedHandler by default to restrict RoleManager to non-static content), and MSDN covers RoleManagerModule along with the rest of the modules in the System.Web. Security namespace, so you could probably find what you need there.
Try adding the following to your block: The RoleManager bit is key, and it's not included in any of the online examples that I could find. Without that, the user's role membership isn't initialized for static content, so role-based authorization will always fail. (Disclaimer: I've pieced this together myself based on my limited understanding of IIS, but it seems to work.) Edit (in response to your comment): Sorry, I don't know much about how RoleManager depends on other modules.
You can view the default IIS configuration by looking at c:\Windows\System32\inetsrv\config\applicationHost. Config (at least, that's the past on my Windows Vista machine) to see the order in which modules are loaded (note the use of managedHandler by default to restrict RoleManager to non-static content), and MSDN covers RoleManagerModule along with the rest of the modules in the System.Web. Security namespace, so you could probably find what you need there.
Thank you for your reply I will make sure to test it these days. – Stilgar Nov 3 '10 at 8:28 It did work. Thanks again.
Can you share a bit more info on how the RoleManager depends on the other modules. I noticed that if I don't remove/add the other modules there seems to be a null reference exception somewhere in the pipeline. – Stilgar Nov 7 '10 at 2:14.
I would say the most likely culprit is that the static files are not being processed by ASP. NET but being left up to IIS. Does it work if you add a wildcard script mapping?
I have an application in an application pool that's running in integrated mode. I have added a handler to system. Web > httpHandlers and I kept getting a 404 result.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.