Documentation for this section has not yet been entered.
The Membership.ApplicationName is used to identify users specific to an application. That is, the same user name can exist in the database for multiple ASP.NET applications that specify a different Membership.ApplicationName. This enables multiple applications to use the same database to store user information without running into duplicate user name conflicts. Alternatively, multiple ASP.NET applications can use the same user database by specifying the same Membership.ApplicationName. The Membership.ApplicationName can be set programmatically or declaratively in the configuration for the Web application.
Because a single default membership provider instance is used for all of the requests served by an System.Web.HttpApplication object, you can have multiple requests executing concurrently and attempting to set the Membership.ApplicationName property value. The Membership.ApplicationName property is not thread safe for multiple writes, and changing the Membership.ApplicationName property value can result in unexpected behavior for multiple users of an application. We recommend that you avoid writing code that allows users to set the Membership.ApplicationName property, unless you must. An example of an application where setting the Membership.ApplicationName property may be required is an administrative application that manages membership data for multiple applications. Such an application should be a single-user application and not a Web application.