1、Enterprise Library for .NET Framework 2.0: Core Architecture,Enterprise Library for .NET Framework 2.0,Major new release of Enterprise Library Designed for Microsoft .NET Framework 2.0 Leverages key new capabilities provided by the platform Certain features from Enterprise Library v1.x have been dep
2、recated in favor of the platform Scenarios and features largely unchanged Public application programming interfaces (APIs) not identical, but changes are minor but many improvements are hiding under the covers!,Key Changes from Enterprise Library 1.x,Configuration now built on System.Configuration C
3、onfiguration Application Block no longer exists Easier to use blocks with or without configuration files Instrumentation configurable and disabled by default Much improved Logging Application Block Flexibility and performance Simpler and more powerful Data Access Application Block Use with OLE-DB, O
4、pen Database Connectivity (ODBC) or any managed provider Most of the Security Application Block has been removed Deprecated in favor of .NET Membership and Profile features,Caching,Security,Data Access,Logging,Exception Handling,Enterprise Library for .NET Framework 2.0,Cryptography,Core,Block Depen
5、dency,Optional Provider Dependency,Caching,Security,Data Access,Logging,Exception Handling,Enterprise Library for .NET Framework 2.0,Plug-in,Config Helpers & Design,Instrumen- tation,Object Builder,Cryptography,Core,Block Dependency,Optional Provider Dependency,Core Architecture,Configuration runtim
6、e Configuration design and tooling Instrumentation Factories and object builder,Configuration in Enterprise Library,All Enterprise Library blocks are configurable Controls how the blocks work in your application Specifies which plug-ins you are using Previous versions of Enterprise Library included
7、a Configuration Application Block Supported reading/writing complex configuration objects from pluggable storage Used by all Enterprise Library blocks, and can be used by customer code In Enterprise Library for .NET Framework 2.0, the requirements are the same but the solution is different,System.Co
8、nfiguration in .NET 2.0,Much more powerful than the Microsoft .NET Framework 1.x classes Supports reading and writing rich graphs of objects Automatic serialization and deserialization between configuration classes and XML using ConfigurationSection and ConfigurationElement Some Enterprise Library 1
9、.x features are not directly supported Storing configuration somewhere other than XML Files Monitoring external changes to configuration,Configuration Runtime,Enterprise Library for .NET Framework 2.0 uses System.Configuration, but provides additional helper classes to provide more functionality All
10、 blocks provide ConfigurationSections which are stored in app.config / web.config by default All System.Configuration features such as encryption and using external files are supported Configuration Runtime helper classes are in the Common assembly Used by all Enterprise Library application blocks C
11、an be used by your apps, but you generally wont need to,Configuration Sources,Application Blocks or Custom Code,IConfigurationSource,SystemConfiguration Source,FileConfiguration Source,SqlConfiguration Source,app.config / web.config,foo.config,app.config / web.configDefault ConfigurationSource = ,Sy
12、stem.Configuration,File Watcher,File Watcher,Configuration Sources,Abstract interface that supports loading/saving configuration and monitoring for changes Two implementations included in the core SystemConfigurationSource defers to System.Configuration to read from default configuration file (plus
13、adds file watchers) FileConfigurationSource defers to System.Configuration but reads from arbitrary files SqlConfigurationSource included as a sample Requires that sections derive from SerializableConfigurationSection,Choosing a Configuration Source,Several ways of choosing a configuration source wh
14、en using Enterprise Library If you access blocks using static faades or factories (Examples: DatabaseFactory, Logger), you will always use the applications default ConfigurationSource: If you define a ConfigurationSources section in your default.config file, you can specify which type of source shou
15、ld be used If you dont have this section, SystemConfigurationSource is used If you use the instance factories (Examples:DatabaseProviderFactory, LogWriterFactory) you can specify a configuration source of your choosing Instantiated directly or using ConfigurationSourceFactory,Configuration Source Ex
16、amples,/ Use default source specified in the app.config / web.config file Database db1 = DatabaseFactory.CreateDatabase(“Sales”);/ Use the specified source you dont need an app.config / web.config file FileConfigurationSource fileSource = new FileConfigurationSource(“tom.config”); DatabaseProviderFa
17、ctory factory = new DatabaseProviderFactory(fileSource); Database db2 = factory.Create(“Sales”);,Change Notifications,IConfigurationSource supports monitoring configuration data for changes AddSectionHandler(string sectionName, ConfigurationChangedEventHandler handler) RemoveSectionHandler(string se
18、ctionName, ConfigurationChangedEventHandler handler) Any code can register for changes and respond accordingly In Enterprise Library, only the Logging Application Block currently registers to receive change notification events,Configuration Design and Tooling,Configuration tool eliminates the need t
19、o edit the blocks XML configuration files Quickly add default configuration for a block Strongly-typed properties and providers Validate configuration before you save No major changes to configuration tool user experience from previous versions of Enterprise Library Configuration design-time subsyst
20、em can be used in your own applications and blocks to provide a similar experience for your users,Configuration Design-Time,Improved API Simple base configuration design manager Better node registration and command registration 3 to 4 simple classes to register your custom provider No more OnSited O
21、ne configuration design manager per section Dependent configuration design managers Easy to interop with any .NET configuration,Instrumentation,All Enterprise Library blocks include instrumentation to assist in development, testing and operations Event Log events Performance Counters Microsoft Windo
22、ws Management Instrumentation (WMI) events All instrumentation is disabled by default, but each type can be individually enabled using the configuration tool Instrumentation code contained in common assembly can be reused in your apps,Enabling Instrumentation,Run the installer classes to create the
23、instrumentation artifacts: Run installservices.bat (using an admin account), or Run installutil.exe over each Enterprise Library assembly (using an admin account), or Create your own installers/MSI that do this Configure instrumentation for your app using the tool,Instrumentation Architecture,Event-
24、driven architecture,Instrumentation Provider Class(es),Instrumentation Listener Class(es),Instrumentation Configuration Settings,WMI,Perf Counters,Event Log,Event,ObjectBuilder,Wires up,Application or Block,calls,Instrumentation Attributes,Instrumentation is wired up using attributes: Instrumentatio
25、nListener Defined on a type within the block or application Specifies which listener will deal with instrumentation events InstrumentationProvider Defined on an event within the block or application Specifies the name of the event being fired InstrumentationConsumer Defined on a method within the in
26、strumentation listener The method contains the instrumentation logic, and the name must match the one used in an InstrumentationProvider declaration,Instrumentation Example,public class Database : IInstrumentationEventProvider DbConnection OpenConnection() / Do stuffinstrumentationProvider.FireConne
27、ctionOpenedEvent();public object GetInstrumentationEventProvider() return instrumentationProvider; ,InstrumentationListener( typeof(DataInstrumentationListener), typeof(DataInstrumentationListenerBinder)public class DataInstrumentationProvider InstrumentationProvider(“ConnectionOpened“)public event
28、EventHandler connectionOpened;public void FireConnectionOpenedEvent() connectionOpened(this, new EventArgs(); ,internal class DataInstrumentationListener : InstrumentationListener public DataInstrumentationListener(string instanceName, bool perfCountersEnabled, bool eventLogEnabled, bool wmiEnabled)
29、 :base(perf, event, wmi) InstrumentationConsumer( “ConnectionOpened“) public void ConnectionOpened(object sender, EventArgs e) if (PerformanceCountersEnabled)connectionOpenedCounter.Increment(); ,Instrumentation Installation Attributes,Running installutil over an instrumented class should install al
30、l required event log sources, WMI schemas and performance counters Enterprise Library provides a ReflectionInstaller which uses reflection to find these, with the help of some attributes HasInstallableResources Indicates that there is instrumentation to install PerformanceCountersDefinition Defines
31、the counters used by the block or app EventLogDefinition Defines the event log sources used by the block or app,Factories and Object Builder,Objects inside application blocks need to be constructed and configured There are different ways you can construct objects depending on what you want to do Use
32、 a default configuration source Use a custom configuration source Dont use any configuration at all Inject instrumentation Although each block is different, all rely on similar types of factories for construction,Object Builder,New subsystem shared between EntLib and Composite UI Application Block R
33、esponsible for building objects inside the application blocks Invoking the necessary custom factory using data from configuration Configuring instrumentation for the blocks Can be leveraged from your own apps, but understanding ObjectBuilder is not required to use Enterprise Library,Core,Application
34、 Block,Factories,Static Factory or faade,Instance Provider Factory,Enterprise LibraryFactory,CustomFactory,Block Objects,Object Builder,Strategies,User Code,Configuration Source,Using Static Facades and Factories,Easiest way to use the blocks Configuration is retrieved from the default configuration
35、 source Instrumentation is wired up (but may be disabled) Results in a call to an instance factory behind the scenes Examples: Dim db As Database = DatabaseFactory.CreateDatabase(“Sales”) Logger.Write(“My message”, “My Category”),Using Instance Provider Factories,You get slightly more control on how
36、 objects are created You can choose your own configuration source Instrumentation is wired up (but may be disabled) Examples: Dim factory As New DatabaseProviderFactory(configSource) Dim db As Database = factory.Create(“Sales”) Dim factory As New LogWriterFactory(configSource) Dim writer As LogWrite
37、r = factory.Create(),Creating Objects Directly,New up the object and any dependent objects yourself Configuration sources are not used Object Builder is not involved Instrumentation will not be automatically wired up (but you can add it yourself) Example: Dim db As SqlDatabase = New SqlDatabase(“server=(local)SQLEXPRESS;database=EntLibQuickStarts;Integrated Security=true“),Resources,Download Enterprise Library and related resources from: http:/ Join the Enterprise Library Community at: http:/ Read blogs from the Enterprise Library team at: http:/
