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

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

Covariance and Contravariance-General Discussion

If you have just started the exploration of .Net Framework 4.0, two terms namely Covariance and Contravariance might have been heard. The concept that these terms encapsulate are used by most developer almost daily, however there has never been any botheration about the terminologies. Now, what actually these terms mean and how are these going to affect us as a developer, if we dive in to the details. The simple answer is it’s always good to know your tools before actually using them. Enough philosophy, let’s get to the business. Starting the discussion let me reiterate that in addition to Covariance and Contravariance, there is another terminology, Invariance. I’ll by start here by diving into the details of Invariance and then proceed further. Invariance: Invariance can be better understood by considering the types in .Net.>net has basically two type, value-types and reference-types. Value types (int, double etc) are invariant i.e. the types can’t be interchanged either ...
1 comment
Read more

WCF-REST Services-Part-I

What is REST? REST stands for Representational State Transfer. REST as described in MSDN, “is an architectural style that can be used to build software in which clients (user agents) can make requests of services (endpoints)”. REST is one way to implement a client-server architectural style. A service that uses the architectural style of REST is generally referred to as a RESTful service or endpoint. RESTful endpoint Building Blocks 1. Resources(What resources would the service Serve/Offer) 2. URI(Identifiers used to represent the resources) 3. HTTP Verbs (What parts of the uniform interface (HTTP verbs) are each URI going to support, like Get/Post etc.) I’ll develop a hypothetical system that will make use of these blocks in the next article, let us consider the theoretical aspects of the REST in this post. Why REST? As explained above, REST internally implements a Client/Server model that can be easily achieved by using SOAP with ASMX or WCF. Just for the discussion sake ...
Post a Comment
Read more