Microsoft Enterprise Library: Part-III

Continuing the exploration of the Enterprise library application blocks, this post will cover the Logging Application Block

Logging Application Block

Logging Application Block can be used to write information to a variety of locations:

1. The event log

2. An e-mail message

3. A database

4. A message queue

5. A text file

6. A Windows Management Instrumentation (WMI) event

7. Custom locations using application block extension points

This link provides the design details of logging application block.

To know about what the logging application block does, refer this link

When to use Logging Block: refer to this link
Would it not be nice if there are pre-defined steps showing how to use this block in all the above 7 mentioned scenarios. If you answered YES, here are the steps.

Feel free to play around with the above mentioned scenarios, before I come up with sample app for these.

Till Next we connect

Happy Learning.

Comments

Asp.Net 4.0: An Overview-Part-III

This is the last post in the series which will explore the following new features of ASP.Net 4.0 Performance Monitoring for Individual Applications in a Single Worker Process Web.config File Refactoring Permanently Redirecting a Page Expanding the Range of Allowable URLs Performance Monitoring for Individual Applications in a Single Worker Process It is a common practice to host multiple ASP.NET applications in a single worker process, In order to increase the number of Web sites that can be hosted on a single server. This practice results in difficulties for server administrators to identify an individual application that is experiencing problems. ASP.NET 4 introduces new resource-monitoring functionality introduced by the CLR. To enable this functionality, following XML configuration snippet is added to the aspnet.config configuration file.(This file is located in the directory where the .NET Framework is installed ) <?xml version="1.0" encoding="UTF-8...

WCF-REST Services-Part-II

HOW REST is implemented in WCF Part-I of the series explored the REST conceptually and this post will explore how REST is implemented in WCF. For REST implementation in WCF, 2 new attributes namely WebGetAttribute and WebInvokeAttribute are introduced in WCF along with a URI template mechanism that enables you to declare the URI and verb to which each method is going to respond. The infrastructure comes in the form of a binding ( WebHttpBinding ) and a behavior ( WebHttpBehavior ) that provide the correct networking stack for using REST. Also, there is some hosting infrastructure help from a custom Service¬Host ( WebServiceHost ) and a ServiceHostFactory ( WebServiceHostFactory ). How WCF Routes messages WCF routes network messages to methods on instances of the classes defined as implementations of the service. Default behavior ( Dispatching ) for WCF is to do this routing based on the concept of action. For this dispatching to work, an action needs to be present in ev...

MVVM and MVP pattern(s) as applicable to SilverLight

There could be more to these design patterns and its applicability in SilverLight, however this article is only intended to present and overview and high-level understanding of how to get started in SilverLight application patterns. SilverLight implements SOLID design guidelines along with a MVVM or MVP design pattern. Figure shown below depicts the comparison of approaches followed in MVVM and MVP pattern. MVVM pattern can follow two approaches 1. View First: The view is responsible for creating an instance of a ViewModel, via databinding to a static resource or setting the data context in the code-behind file. Databinding approach UserControl.Resources local:SampleViewModel x:Key=” ViewModel ” / UserControl.Resources Grid DataContext=”{Binding Path= Object , Grid is bound to object that is obviously in Model. Code Behind approach this.DataContext = new SampleV...

.Net Advanced Concepts

Search This Blog