Migrating from ASP.NET 1.x to 2.0
Migrating from ASP.NET 1.x
If you have ASP.NET 1.x applications in production, you will be relieved to know that ASP.NET 2.0 is fully backwards compatible. That is, your ASP.NET 1.x applications will run as normal on ASP.NET 2.0 without any changes. However, you will notice many changes when you upgrade to Visual Studio 2005. In particular, the default development model for ASP.NET pages has changed. In addition, with ASP.NET 2.0, you will have a variety of new compilation and deployment options. All of these changes will be discussed in detail in the following sections.
Changes in Architecture
The fundamental architecture of ASP.NET has always been designed for flexibility and extensibility. ASP.NET 2.0 continues this tradition by incorporating a new provider model to support many of the new features. New utilities and API's have been added to improve site maintenance and improve configuration. All of these changes are designed to make developing ASP.NET 2.0 applications a faster and more streamlined process, while still providing the flexibility and extensibility that developers were used to with ASP.NET 1.x.
The Provider Model
Many of the new features in ASP.NET 2.0 depend on communication between the Web application and a data store. In order to provide this access in a consistent fashion, ASP.NET 2.0 uses a set of providers. A provider is both a pattern and a point where developers can extend the ASP.NET 2.0 framework to meet specific data-store needs. For example, a developer can create a new provider to support the user identification system, or to store personalization data in an alternate data store.
Most custom providers will interact with database backend systems. However, the programmer is free to implement the required provider methods and classes using any medium or algorithm, so long as it meets the model's required interface specification.
ASP.NET 2.0 Providers
The provider model defines a set of interfaces and hooks into the data persistence layer that provides storage and retrieval for specified requests. In this way the provider model acts as a programming specification that allows ASP.NET 2.0 to service unique client concerns.
ASP.NET 2.0 uses a wide variety of providers, including:
Membership. The membership provider supports user authentication and user management.
Profile. The profile provider supports storage and retrieval of user-specific data linked to a profile.
Personalization. The personalization provider supports persistence of Web Part configurations and layouts for each user.
Site Navigation. The site navigation provider maps the physical storage locations of ASP.NET pages with a logical model that can be used for in-site navigation and linked to the various new navigation controls.
Data providers. ADO.NET has always used a provider model to facilitate the connection between a database and the ADO.NET API. ASP.NET 2.0 builds upon the data provider by encapsulating many of the ADO.NET data calls in a new object called a data source.
Each type of provider acts independently of the other providers. You can therefore replace the profile provider without causing problems with the membership provider.
continued...
If you have ASP.NET 1.x applications in production, you will be relieved to know that ASP.NET 2.0 is fully backwards compatible. That is, your ASP.NET 1.x applications will run as normal on ASP.NET 2.0 without any changes. However, you will notice many changes when you upgrade to Visual Studio 2005. In particular, the default development model for ASP.NET pages has changed. In addition, with ASP.NET 2.0, you will have a variety of new compilation and deployment options. All of these changes will be discussed in detail in the following sections.
Changes in Architecture
The fundamental architecture of ASP.NET has always been designed for flexibility and extensibility. ASP.NET 2.0 continues this tradition by incorporating a new provider model to support many of the new features. New utilities and API's have been added to improve site maintenance and improve configuration. All of these changes are designed to make developing ASP.NET 2.0 applications a faster and more streamlined process, while still providing the flexibility and extensibility that developers were used to with ASP.NET 1.x.
The Provider Model
Many of the new features in ASP.NET 2.0 depend on communication between the Web application and a data store. In order to provide this access in a consistent fashion, ASP.NET 2.0 uses a set of providers. A provider is both a pattern and a point where developers can extend the ASP.NET 2.0 framework to meet specific data-store needs. For example, a developer can create a new provider to support the user identification system, or to store personalization data in an alternate data store.
Most custom providers will interact with database backend systems. However, the programmer is free to implement the required provider methods and classes using any medium or algorithm, so long as it meets the model's required interface specification.
ASP.NET 2.0 Providers
The provider model defines a set of interfaces and hooks into the data persistence layer that provides storage and retrieval for specified requests. In this way the provider model acts as a programming specification that allows ASP.NET 2.0 to service unique client concerns.
ASP.NET 2.0 uses a wide variety of providers, including:
Membership. The membership provider supports user authentication and user management.
Profile. The profile provider supports storage and retrieval of user-specific data linked to a profile.
Personalization. The personalization provider supports persistence of Web Part configurations and layouts for each user.
Site Navigation. The site navigation provider maps the physical storage locations of ASP.NET pages with a logical model that can be used for in-site navigation and linked to the various new navigation controls.
Data providers. ADO.NET has always used a provider model to facilitate the connection between a database and the ADO.NET API. ASP.NET 2.0 builds upon the data provider by encapsulating many of the ADO.NET data calls in a new object called a data source.
Each type of provider acts independently of the other providers. You can therefore replace the profile provider without causing problems with the membership provider.
continued...
posted by Mayur @ 1:23 PM
0 Comments:
Post a Comment
Subscribe to Post Comments [Atom]
<< Home