At the top of the diagram, you see the ASP.NET 4.5 websites and web applications that represent
the websites that you build. These websites can contain controls like the login controls (discussed
next) that in turn can talk to the ASP.NET application services such as membership and roles.
To create a flexible solution, these services don’t talk to an underlying data source directly, but
instead talk to a configured provider. A provider is an interchangeable piece of software that is
designed for a specific task. For example, in the case of the membership services, the Membership
provider is designed to work with users in the underlying data store. You can configure different
providers for the same application service depending on your needs. Previous versions of ASP.NET
shipped with a SQL Server provider that enables your membership services to talk to a SQL Server
database (both the Express and commercial editions) and an Active Directory provider (that lets you
create and manage users in Active Directory on Windows). These providers are still available, but
there is now a new alternative. In June 2011, Microsoft released the Universal Providers that work
the same as the SQL Server providers, but can be used to target all editions of SQL Server, including
SQL Server Compact and SQL Azure. This makes it easy to switch the underlying database, simply
by changing the configuration for the application. The Universal Providers are available for .NET 4
and .NET 4.5 and are ideal for Internet-connected websites like PlanetWrox.com. If you create a
new ASP.NET Web Forms site, the Universal Providers are already set up for you. If you create an
empty ASP.NET website instead (as is the case with the Planet Wrox sample project), you need to
add the providers yourself using NuGet, as you see in a later exercise.
At the top of the diagram, you see the ASP.NET 4.5 websites and web applications that representthe websites that you build. These websites can contain controls like the login controls (discussednext) that in turn can talk to the ASP.NET application services such as membership and roles.To create a flexible solution, these services don’t talk to an underlying data source directly, butinstead talk to a configured provider. A provider is an interchangeable piece of software that isdesigned for a specific task. For example, in the case of the membership services, the Membershipprovider is designed to work with users in the underlying data store. You can configure differentproviders for the same application service depending on your needs. Previous versions of ASP.NETshipped with a SQL Server provider that enables your membership services to talk to a SQL Serverdatabase (both the Express and commercial editions) and an Active Directory provider (that lets youcreate and manage users in Active Directory on Windows). These providers are still available, butthere is now a new alternative. In June 2011, Microsoft released the Universal Providers that workthe same as the SQL Server providers, but can be used to target all editions of SQL Server, includingSQL Server Compact and SQL Azure. This makes it easy to switch the underlying database, simplyby changing the configuration for the application. The Universal Providers are available for .NET 4and .NET 4.5 and are ideal for Internet-connected websites like PlanetWrox.com. If you create anew ASP.NET Web Forms site, the Universal Providers are already set up for you. If you create anempty ASP.NET website instead (as is the case with the Planet Wrox sample project), you need toadd the providers yourself using NuGet, as you see in a later exercise.
การแปล กรุณารอสักครู่..