本文发表在 rolia.net 枫下论坛Data Access Application Block : data access helper component, SqlHelper， Use it if you are using SQL Server as the database and wish to reduce the amount of data access code you write. Can use it internally in your own data access classes. Versions of SqlHelper for OleDb and Oracle written in C# are included in the Nile 3.0 sample application.
Exception Management Application Block : Use it as the basis for your exception handling framework. Ideal for applications that use exception chaining or wrapping and pass exceptions up the call stack. Custom publishers can be used to log exception information to shared databases.
Aggregation Application Block : Use it when your application needs to bring together data from various sources and those sources may change over time. The Aggregation Block serves to abstract the underlying data sources.
Asynchronous Invocation Application Block: Use it when the data sources your application communicates with may require a lengthy call. Using the Async Block makes it appear as if the application is more responsive by allowing Web pages to be built incrementally.
Caching Application Block : Use it when you need to cache data in Windows Forms or other non-Web based applications. ASP.NET provides its own cache and so would not typically be required for Web applications. Very useful for improving performance.
Configuration Management Application Block: Use it when your application might require its configuration data to be stored in different locations at different times. Also take advantage of it for encrypting sensitive information.
Updater Application Block : Use it when your application needs to auto-update with new assemblies or when you are writing a service to provide client machines with updates to a variety of applications.
User Interface Process Application Block : Use it when you need to implement the same process in different types of applications (Windows Forms, Web forms) or want to allow users to resume a session at a later time. Also ideal for wizard-based applications.更多精彩文章及讨论，请光临枫下论坛 rolia.net
Exception Management Application Block : Use it as the basis for your exception handling framework. Ideal for applications that use exception chaining or wrapping and pass exceptions up the call stack. Custom publishers can be used to log exception information to shared databases.
Aggregation Application Block : Use it when your application needs to bring together data from various sources and those sources may change over time. The Aggregation Block serves to abstract the underlying data sources.
Asynchronous Invocation Application Block: Use it when the data sources your application communicates with may require a lengthy call. Using the Async Block makes it appear as if the application is more responsive by allowing Web pages to be built incrementally.
Caching Application Block : Use it when you need to cache data in Windows Forms or other non-Web based applications. ASP.NET provides its own cache and so would not typically be required for Web applications. Very useful for improving performance.
Configuration Management Application Block: Use it when your application might require its configuration data to be stored in different locations at different times. Also take advantage of it for encrypting sensitive information.
Updater Application Block : Use it when your application needs to auto-update with new assemblies or when you are writing a service to provide client machines with updates to a variety of applications.
User Interface Process Application Block : Use it when you need to implement the same process in different types of applications (Windows Forms, Web forms) or want to allow users to resume a session at a later time. Also ideal for wizard-based applications.更多精彩文章及讨论，请光临枫下论坛 rolia.net