Re: roleManager providers
- From: "MikeS" <michael.spencer@xxxxxxxxx>
- Date: 25 Dec 2005 08:03:07 -0800
I assume the use of multiple role providers is so one can change the
provider as a user navigates to a different location in the site.
However if I something like this:
<location path="Premium">
<system.web>
<roleManager defaultProvider="Premium" />
It produces this build error:
Error 102 It is an error to use a section registered as
allowDefinition='MachineToApplication' beyond application level. This
error can be caused by a virtual directory not being configured as an
application in IIS.
Even though the Premium directory is configured as an IIS application.
So is this feature broken or am I using it incorrectly?
.
- References:
- roleManager providers
- From: MikeS
- roleManager providers
- Prev by Date: Re: When exactly Application_AuthenticateRequest event is fired?
- Next by Date: ASP.NET 2.0 Multiple Membership Providers for Authentication
- Previous by thread: roleManager providers
- Next by thread: Re: Insufficient access rights to perform the operation
- Index(es):