Hi Daniel,
There is problem in the built in implementation that probably cause the problem you have. We have already fixed the problem, but the fix will be available with the next SP in the beginning of March.
Meanwhile you can fix the problem by implementing custom and then your custom membership provider should inherit from this interface.
using System.Web.Security;
using Telerik.Framework.Security;
public class MyMembershipProvider : SqlMembershipProvider, CustomIExtendedMembershipProvider
{
public MembershipUserCollection GetAllUsers(int from, int maxRows, string sortExpr, out int totalRows)
{
return base.GetAllUsers(from, maxRows, out totalRows);
}
public MembershipUserCollection FindUsersByName(string usernameToMatch, int from, int maxRows, string sortExpr, out int totalRows)
{
return base.FindUsersByName(usernameToMatch, from, maxRows, out totalRows);
}
public MembershipUserCollection FindUsersByEmail(string emailToMatch, int from, int maxRows, string sortExpr, out int totalRows)
{
return base.FindUsersByEmail(emailToMatch, from, maxRows, out totalRows);
}
public MembershipUserCollection GetUsersInRole(string roleName, int from, int maxRows, string sortExpr, out int totalRows)
{
// implement a logic for returning users in the specified role
totalRows = 0;
return new MembershipUserCollection();
}
}
CustomIEdtendedMembershipProvider
Sincerely yours,
Ivan Dimitrov
the Telerik team
Watch a
video
on how to optimize your support resource searches and
check out more tips
on the blogs.
Follow the status of features or bugs in
PITS
and vote for them to affect their priority.