Skip to main content

Microsoft Enterprise Library: Part-II

This post is in continuation to the series started for exploring the Enterprise library here. This post will cover in detail the newly introduced Unity Application Block.


Before we start the discussion there are few concepts that need to be understood for getting a good grasp of the Block.

Inversion of Control (IoC): It means that objects do not create other objects on which they rely to do their work. Instead, they get the objects that they need from an outside source.

Dependency Injection (DI): It means that this is done without the object intervention, usually by a framework component that passes constructor parameters and set properties.

More about DI can be found here

IOC is implemented using DI (Dependency injection).

IOC is a principle while DI is a way of implementing IOC. In DI we have four broader ways of implementing the same:

• Constructor way

• Exposing setter and getter

• Interface implementation

• Service locator


These two concepts forms the basis of this block and more details about these can be found here. (Although it takes JAVA as the language, the concept is applicable to .Net and any other language that implements these patterns).


MSDN has a great article for introduction to Unity
More about the Unity Block can be read here



Following Links contain the implementations –With Code

Link1

Link2

Hope this was useful,

Till Next We Connect….

Happy Learning.

Labels:

Comments

Post a Comment

Popular posts from this blog

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...
Post a Comment
Read more

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...
Post a Comment
Read more

WPF Routing

WPF (3.5) introduced the concept of Routing that made the event routing easies in the scenarios where it was tedious to handle events. Consider a scenario where there are a number of Hyperlinks in a Panel that direct to separate locations on Click. Now if this is done in normal programming, each hyperlink will have to have code for execution. It would be easier and cleaner if we could handle the hyperlinks in the container (the Panel) that handles the click and redirects to appropriate location. WPF handles the events with the following 3 strategies. Direct events are like ordinary .NET events. They originate in one element and don’t pass to any other. For example, MouseEnter is a direct event. Bubbling events are events that travel up the containment hierarchy. For example, MouseDown is a bubbling event. It is raised first by the element that is clicked. Next, it is raised by that element’s parent, and then by that element’s parent, and so on, until WPF reaches the top of the e...
Post a Comment
Read more