By: Satish Balakrishnan. Dictionary Dictionary Term of the Day. High-Performance Cloud Computing. Techopedia Terms. Connect with us. Sign up. Term of the Day. Best of Techopedia weekly. News and Special Offers occasional. Microsoft Enterprise Library.
Techopedia Explains Microsoft Enterprise Library. Techopedia Explains Microsoft Enterprise Library The Microsoft Enterprise Library is freely available in the form of source code and pluggable binaries, which can be easily customized by developers to suit their development needs. In particular, the LAB is useful if you need to filter logging messages based on category or priority, if you need to format the messages, or if you need to change the destination of the message without changing the application code.
A logging capability can be added to an application by adding an entry to an applications configuration file either app. This tool contains specific instructions in order to enable the Logging Application Block. Alternatively, in the app. EnableLoggingApplicationBlock to true.
A following C code snippet shows the loggingConfiguration property of the app. Setting either of these properties to false disables the logging block. NET Entity Framework canonical query tree. Type the name of the new category, and then press Enter. By default, all logging levels are enabled. The Configuration section appears in the right pane. The LAB that you configured must be added to the app. The following settings can be used to enable and configure data provider interaction with the LAB.
The following code fragment provides an example of a Logging Application Block that could be added to a Zen data access application. TextFormatter, Microsoft. The following sources provide additional information about using Application Blocks:.
Often I'll use the Data and Logging components together and that feels like enough functionality to justify the size. If your app is strictly on the server side then this really isn't too much of an issue. One of the things that is nice about it is that if you need more than one block you don't have to go to multiple implementations from multiple vendors that are configured in different ways.
They also provide a tool to help with the configuration that's a plus and a minus, a plus that they make it easy, a minus that they NEED a tool to help configure it. I've had the pleasure of being invinted to a couple of Patterns and Practices workshops where I was working side by side with the team members who wrote EntLib.
The intent in creating EntLib was to implement Microsoft's Best Practices in common components that everyone needs that are not part of the base Framework. They are very stable, provide very good performance and very good flexibility. I would start by using some of the easier blocks, like Data and Logging. They're not too hard to configure and get started with.
Then once you understand those it will be a bit easier to move on to some of the other blocks. I have not found a situation where you shouldn't use them, other than when you don't need them. There is a lot of good stuff in EntLib, but there are reasons those things are not in the full framework. The logging stuff is excellent, but the data parts have been surpassed by later additions to full framework in my opinion.
I have also found that some of the blocks do not fit very well in certain situations. As mentioned the overhead is significant in some cases as well and the config can be quite confusing. Most of my apps have some degree of performance constraints, so I tend to use the EntLib stuff as an example and write my own features more often than using the EntLib things.
Sign up to join this community. The best answers are voted up and rise to the top.
0コメント