Then I'd suggest running this in debug mode with the source code project for
your role provider in the solution. Set breakpoints at the appropriate places
and trace through your code to find out what may be wrong.
If your breakpoints don't get hit, that means your configuration setup is
wrong.
Peter
--
Site:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com
Short urls & more:
http://ittyurl.net
"Tom Van den Brandt" wrote:
> Yes, I do...
>
> Here's a section from my web.config:
>
>
> <roleManager defaultProvider="CustomRoleProvider"
> enabled="true"
> >
> <providers>
> <clear />
> <remove name="AspNetSqlRoleProvider"/>
> <add
> name="CustomRoleProvider"
> type="CustomRoleProvider"
> connectionString="server=rakels10.synstar.be;database=websupporttables;user
> id=xxxxx password=xxxxx;"
> applicationName="/"
> writeExceptionsToEventLog="false" />
> </providers>
> </roleManager>
>
>
> I don't get it, I have a testpage where I try some of the methods from
> my custom role provider and this works... e.g.:
>
> Dim provider As RoleProvider = New CustomRoleProvider
> Dim roles() As String = provider.FindUsersInRole("user", "%")
> ...
>
>
> Peter Bromberg [C# MVP] schreef:
> > Do you have this set up properly in your web.config entries? Do you have a
> > "remove name=XXx" at the top of the section to remove the default roles
> > provider before you add your entry for your custom one?
> > Peter
> >
>