ProfileManager.ApplicationName Property

Gets or sets the name of the application for which to store and retrieve profile information.

Namespace:  System.Web.Profile
Assembly:  System.Web (in System.Web.dll)

public static string ApplicationName { get; set; }

Property Value

Type: System.String
The name of the application for which to store and retrieve profile information.

The ProfileManager uses the ApplicationName property to associate profile information with different applications. This enables multiple applications to use the same database to store user information without running into conflicts between duplicate users. Multiple ASP.NET applications can use the same user 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 by using the applicationName attribute.

If a value is not specified for the applicationName attribute in the configuration file for the Web application, then the profile providers included with the .NET Framework use the ApplicationVirtualPath property value for ASP.NET applications. For non-ASP.NET applications, the default value is the ModuleName property value, without the file extension.

The ApplicationName property exposes the SettingsProvider.ApplicationName property of the default profile provider. The default profile provider is specified using the defaultProvider attribute of the profile configuration element. If the user profile contains properties that are managed by a profile provider other than the default provider, they may be configured with a different application name. To access the application name of a profile provider other than the default provider, obtain a reference to the profile provider using the Providers property and access the ApplicationName property of the provider directly.

Caution noteCaution

Because a single default profile 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 require it. An example of an application where setting the ApplicationName property may be required is an administrative application that manages profile data for multiple applications. Such an application should be a single-user application and not a Web application.

The following configuration file excerpt shows the profile element in the system.web section of the Web.config file for an ASP.NET application. It sets the application's default profile provider to a SqlProfileProvider instance and sets the ApplicationName to MyApplication.

<profile enabled="true" defaultProvider="SqlProvider">
  <providers>
  <add name="SqlProvider"
    type="System.Web.Profile.SqlProfileProvider"
    connectionStringName="SqlServices"
    applicationName="MyApplication" />
  </providers>
</profile>

.NET Framework

Supported in: 4.5.2, 4.5.1, 4.5, 4, 3.5, 3.0, 2.0

Windows 8.1, Windows Server 2012 R2, Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft