Assembly: System.Web (in system.web.dll)
/** @property */ public String get_ApplicationName () /** @property */ public void set_ApplicationName (String value)
public override function get ApplicationName () : String public override function set ApplicationName (value : String)
Property ValueThe name of the application for which to store and retrieve role information. The default is the System.Web.HttpRequest.ApplicationPath property value for the current System.Web.HttpContext.Request.
The ApplicationName is used by the SqlRoleProvider to associate users and roles with different applications. This enables multiple applications to use the same database to store user and role information without running into conflicts between duplicate user names or role names. Multiple ASP.NET applications can use the same database by specifying the same value in the ApplicationName property. The ApplicationName property can be set programmatically, or it can be set declaratively in the configuration file for the Web application using the applicationName attribute.
If a value is not specified for the applicationName attribute in the configuration file for the Web application, then the System.Web.HttpRequest.ApplicationPath property value for the current System.Web.HttpContext.Request object is used.
Because a single default role provider instance is used for all of the requests served by an HttpApplication object, you can have multiple requests executing concurrently and attempting to set the ApplicationName property value. The ApplicationName property is not thread safe for multiple writes, and changing the ApplicationName property value can result in unexpected behavior for multiple users of an application. It is recommended that you avoid writing code that allows users to set the ApplicationName property unless you must. An example of an application where setting the ApplicationName property may be required is an administrative application that manages role data for multiple applications. Such an application should be a single-user application and not a Web application.
The following example shows the roleManager element in the system.web section of the Web.config file for an ASP.NET application. It specifies the application's SqlRoleProvider instance and sets the ApplicationName property to
<roleManager defaultProvider="SqlProvider" enabled="true" cacheRolesInCookie="true" cookieName=".ASPROLES" cookieTimeout="30" cookiePath="/" cookieRequireSSL="false" cookieSlidingExpiration="true" cookieProtection="All" > <providers> <add name="SqlProvider" type="System.Web.Security.SqlRoleProvider" connectionStringName="SqlServices" applicationName="MyApplication" /> </providers> </roleManager>