roleManager defaultProvider

What I am trying to do is change the roles a user is a member of based
on where they navigate to into in a site.

So what is the point of having multiple roleManager providers? Is
defaultProvider required? If I omit defaultProvider can ASP.NET
determine which provider to use based on ApplicationVirtualPath or
something? If so then how do I set that up in ADAM when I have nested
applications? Or else can I do that myself somehow even though
Roles.Provider is read only? Do scopes play into any part of this? Do I
have to set up the same provider with a different application name in
every subdirectorys web config?

I think I could use a single provider but changing the
Provider.ApplicationName applies to the application and not to the
session. Why is that?

.

Relevant Pages

  • Problems with the RoleProvider
    ... I recently develop a custom membership provider and role ... SharePoint when the user is listed as a member of the site, ... GetRolesForUser in my role provider and that is returning an array ...
    (microsoft.public.dotnet.framework.aspnet)
  • Role Provider not working
    ... I recently develop a custom membership provider and role ... I did configure the central admin and the SharePoint site ... SharePoint when the user is listed as a member of the site, ... GetRolesForUser in my role provider and that is returning an array ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: (msh) get-command does not work in variable provider
    ... Looks like get command is trying to navigate over current provider. ... Please open a bug. ...
    (microsoft.public.windows.server.scripting)
  • Re: query design issue
    ... Create a main report of just each unique Provider. ... a multi-column subreport that is based on the Provider and Member records. ... Set the subreport to display across then down. ...
    (microsoft.public.access.queries)
  • Re: Forms authentication credentials fail
    ... setup I had that got it through. ... Thanks for the provider though, it should so be included in the ... not implement inherited abstract member ... I haven't quite got my head around forms authentication vs membership ...
    (microsoft.public.dotnet.framework.aspnet.security)