Visual Basic (Declaration)

<AspNetHostingPermissionAttribute(SecurityAction.InheritanceDemand, Level := AspNetHostingPermissionLevel.Minimal)> _
<AspNetHostingPermissionAttribute(SecurityAction.LinkDemand, Level := AspNetHostingPermissionLevel.Minimal)> _
Public MustInherit Class ProfileProvider _
    Inherits SettingsProvider

Visual Basic (Usage)

Dim instance As ProfileProvider

C#

[AspNetHostingPermissionAttribute(SecurityAction.InheritanceDemand, Level = AspNetHostingPermissionLevel.Minimal)]
[AspNetHostingPermissionAttribute(SecurityAction.LinkDemand, Level = AspNetHostingPermissionLevel.Minimal)]
public abstract class ProfileProvider : SettingsProvider

Visual C++

[AspNetHostingPermissionAttribute(SecurityAction::InheritanceDemand, Level = AspNetHostingPermissionLevel::Minimal)]
[AspNetHostingPermissionAttribute(SecurityAction::LinkDemand, Level = AspNetHostingPermissionLevel::Minimal)]
public ref class ProfileProvider abstract : public SettingsProvider

JScript

public abstract class ProfileProvider extends SettingsProvider

ASP.NET profiles offer persistent storage and retrieval of user-specific properties. Profile property values and information are stored in a data source in a manner determined by the ProfileProvider implementation. You can use the profile providers that are included with the .NET Framework (represented by the classes that derive from the ProfileProvider abstract class), or you can implement your own provider by creating a new class that derives from ProfileProvider.

There are two primary reasons for creating a custom profile provider.

• You need to store profile information in a data source that is not supported by the profile providers included with the .NET Framework, such as a FoxPro database, an Oracle database, or other data stores.

• You need to manage profile information using a database schema that is different from the database schema used by the providers that ship with the .NET Framework. A common example of this would be user data that already exists in a SQL Server database for a company network or a Web site.

The ProfileProvider abstract class inherits from the SettingsProvider abstract class, which inherits from the ProviderBase abstract class. Classes that implement ProfileProvider must also implement the required members of the SettingsProvider and ProviderBase abstract classes. For more information about implementing a profile provider, see Implementing a Profile Provider.

Topic	Location
Implementing a Profile Provider	Building ASP .NET Web Applications
Implementing a Profile Provider	Building ASP .NET Web Applications
Implementing a Profile Provider	Building ASP .NET Web Applications in Visual Studio
Implementing a Profile Provider	Building ASP .NET Web Applications in Visual Studio

For an example of a ProfileProvider implementation, see How to: Build and Run the Profile Provider Example.

• AspNetHostingPermission 

  for operating in a hosted environment. Demand value: LinkDemand; Permission value: Minimal.

• AspNetHostingPermission 

  for operating in a hosted environment. Demand value: InheritanceDemand; Permission value: Minimal.

System..::.Object
  System.Configuration.Provider..::.ProviderBase
    System.Configuration..::.SettingsProvider
      System.Web.Profile..::.ProfileProvider
        System.Web.Profile..::.SqlProfileProvider

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Windows 7, Windows Vista, Windows XP SP2, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP Starter Edition, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows Server 2000 SP4, Windows Millennium Edition, Windows 98

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

.NET Framework

Supported in: 3.5, 3.0, 2.0

Reference

Other Resources