Enterprise Library 5.0 Research <1> Understanding Enterprise Library 5.0

Microsoft has just released the Enterprise Library 5.0, which has too many bright spots compared to the 4.x. Because of these bright spots, I have to learn and understand the 5.0 desire.

< what is Enterprise Library>: According to Microsoft's definition, the Enterprise Library is made up of several application modules and core infrastructure components that are reusable and can help programmers to solve the commonality problems in enterprise-level development. Admittedly, in enterprise development, caching, encryption, database access, exception handling, log, security, verification and other issues are inevitable problems. But for a long time, Microsoft has not provided official guidance, until the advent of the Enterprise Library, we see hope, and with the Enterprise Library version of the update, we found that the processing mechanism is more mature. This is a boon for all. NET programmers and architects, but it is a pity that the Enterprise Library does not see signs of large-scale deployment at home.

What <enterprise Library 5.0 has: in Enterprise Library 5.0, the most intuitive thing we can see is a visual configuration tool where all of the component's properties can be dragged and towed. Configuring added components here can be invoked through dependency injection (IOC) into the application. Here we can think of spring, and it's also very thoughtful of Microsoft to manage generic components in a way that unifies the lifecycle.

Look at this sentence: "In this release of Enterprise Library, the underlying technique for creating objects uses a single dependency injec tion container; WithUnity as the default container. It fully encompasses the move to using dependency injection techniques through Unity to instantiate objects. You can use the container to generate instances of Enterprise Library objects and inject them into other objects. "From here we can see unity as a single example of the dependency injection container definition. And Object-builder, this low-level injection mechanism, is also incorporated into unity in this version, so we no longer have to reference or assign object Builder assembly in the project. On the unity of the specific how the operation, we later in the article to carry out in-depth research.

Also, from the release pack, we can see that Enterprise Library 5.0 provides two entrances to VS 2008 and VS 2010, and provides a lot of Enterprise Library test code and source code. If you have the time, you can continue to study later.

Then, in addition to the cryptography Application Block and security application blocks, there is no adjustment, and the other components are somewhat changed.

Where <enterprise Library 5.0 can be used. : In many enterprise-class applications must be the same requirements, it provides a rich solution; it has very good scalability, and if you are developing custom components, it provides a foundation; all of the components underneath the library are self-contained, and if you only need to use one of them you don't need to load all the packages Wait

In short, the above content is only a basic introduction to the Enterprise Library 5.0, in the future, I will Enterprise Library 5.0 in the various components to carry out a number of more detailed research and introduction.