Configures the location of a custom implementation of the role service.
Assembly: System.Web.Extensions (in System.Web.Extensions.dll)
Determines whether the specified object is equal to the current object.(Inherited from Object.)
Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.(Inherited from Object.)
Serves as the default hash function. (Inherited from Object.)
Returns a string that represents the current object.(Inherited from Object.)
The role Web service is used by AJAX-enabled applications to retrieve role information for the current authenticated user by using an asynchronous Web service call. You can useto provide the path of an alternative implementation of the role Web service instead of using the built-in Web service.
To use the role service in your application, you must enable it in the configuration file and declare it in the page. If you use the built-in role Web service, you have to enable it, but you do not have to explicitly declare the role service manager in the page.
To create a custom role service, you must implement a Web service that has two methods: GetRolesForCurrentUser and IsCurrentUserInRole. These methods must have the same signature as the corresponding methods of the built-in role Web service.
The following example shows the basic class structure that must be implemented in a custom role Web service class.
To use a custom role Web service, you can add the service declaratively in markup by putting a RoleService element inside the ScriptManager control, as shown in the following example.
<asp:ScriptManager ID="SM1" runat="server"> <RoleService Path="MyRoleService.asmx" LoadRoles="true" /> </asp:ScriptManager>
You can also programmatically set the Path property to use a custom role Web service.
Available since 3.5
Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.