Microsoft enterprise database 4.1 Study Notes (11) Core class of the enterprise database

Many common functions are implemented in many modules of the Enterprise Library. They are also useful for application code outside the Enterprise Library. For example, data serialization and access configuration information. To provide availability, these codes are all placed in the common program set at the core of the Enterprise Library.

In addition, all modules are designed with minimal dependencies so that they can be used independently. Except for unity, all enterprise libraries depend on the core library of the Enterprise Library. The core library includes the following subsystems:

• Common Assembly
• Module dashboard and module running status
• Configuration information help class and support components during design

 

1. Common Assembly

The Enterprise Library contains an assembly called common, which contains some useful functions used by other modules. To use any module of the Enterprise Library (except the unity module), you must add a reference to this Assembly. By providing some common functions, we can reduce the degree of dependency between modules.

2. dashboard

Most modules provide dashboards. The dashboard types are as follows:

• Performance counters
• Event Log
• WMI event

The collections class is part of the core class library and is in the Common Assembly. You can use it in your application.

By default, the meter function is disabled. You can use the enterprise database configuration tool to activate each type of meter function. If you have administrative privileges, you can use installutil.exe to install the instrument.

Some function modules rely on the instrumentation function to be packaged in a single module. For example, the exception handling module uses the logging module to record the exception information, but this is not necessary. You can record the exception information elsewhere and record it in the event log, alternatively, you can expand the exception handling module to provide a custom exception information log provider.

3. configuration information help class and support components during design

The configuration information uses the system. Configuration namespace, which makes it easy to use the configuration information of the Enterprise Library module. Use the factory to create and configure the Enterprise Library objects in the configuration file. You can also use other types of content to replace the XML file as the configuration source. For example, you can use the SQL Server database. You can also create an object without a configuration file. You can use the constructor to create an object.

To support expansion, you can also use the configuration help class in addition to the system. Configuration namespace. The help class supports polymorphism sets, generic sets, and configuration sources. These improvements require that the configuration be based on the dependency injection mode, not the provider mode.

The enterprise database configuration tool allows you to modify the configuration information without modifying the XML file. With configuration tools that support components during design, you can enjoy a more friendly user experience.

Http://www.cnblogs.com/virusswb/archive/2010/04/18/1714942.html