Wednesday, June 8, 2011

Common Design Principles

There are number of common design principles that, like design patterns, best practice over the years to build maintainable software.

I'm up to describe some widely used design principles though out the post.

Following common principle are extracted by the same book that I mentioned before (Professional ASP.Net Design Patterns - Scott Millet).

Principles are as follows:

Keep It Simple Stupid (KISS)
One common issue in software programming is over-complicating a solution. So main concern of this principle is keep the code simple but not simplistic. Eventually this will avoid unnecessary complexities.

Don't Repeat yourself (DRY)
Main concern of this principle is to avoid the repetition. In other words this is all about abstracting out the common functionalities into a single place.
Ex: If there is a price calculation method in a system. It should lay in a single place there.

Tell Don't Ask
The Tell, Don’t Ask principle is closely aligned with encapsulation and the assigning
of responsibilities to their correct classes. This principle state that you should tell the
object to what actions that you want to perform instead of checking the state of an object and performing the action by yourself. This avoids the tight coupling between classes.

You Ain’t Gonna Need It (YAGNI)
This is about putting of any features that are going to add having the idea in mind, that you gonna need this later. A design methodology that adheres to YAGNI is test-driven development (TDD). In brief TDD is all about righting the code only to pass the test.

Separation of Concerns (SoC)
SoC is the process of dissecting a piece of software into distinct features that encapsulate unique behavior and data that can be used by other classes. Generally, a concern represents a feature or behavior of a class. The act of separating a program into discrete responsibilities significantly increases code reuse, maintenance, and testability.

So this is it.

Tuesday, March 8, 2011

S.O.L.I.D Design Principles

Hold on!!! Before this please read the common design principle post.

After a long time thought of writing a post. Actually these days I'm reading a book which is written by Scott Millet and the name of the book is "Professional ASP.Net Design Patterns". I can guarantee that this book give you a great knowledge on design stuffs.

Most of us are bit lazy to read things, so I thought of posting the things that I got form it. This is like the cream of what I got.

I'll start it with the S.O.L.I.D design principles:

The term S.O.L.I.D. comes from the initial letter of each of the five principles that were collected in the book Agile Principles, Patterns, and Practices in C# by Robert C. Martin, or Uncle Bob to his friends. Simply this is a collection of best practices for object-oriented design.

Following will explain all the principles:

Single Responsibility Principle (SRP)
This principle is closely aligned with a common design principle called Separation of Concerns. It says that every object should have one reason to change and single focus of responsibility. By applying this principle, you avoid the problem of monolithic class design. At the same time this principle gives readability and maintenance for a system.

Open-Closed Principle (OCP)
This principle says that classes should be open for extension and closed for modification, in that you should be able to add features and extend a class without it changing its internal behavior. In other words it avoids the possibilities of braking the system.

Liskov Substitution Principe (LSP)
The LSP says that you should be able to use any derived class in place of a base class and have it behave in the same manner without modification. In other words derived classes must be substitutable for their base classes.

Interface Segregation Principle (ISP)
The ISP is all about splitting the methods of a contract into groups of responsibility and assigning
interfaces to these groups to prevent a client from needing to implement one large interface and a host of methods that they do not use. The purpose behind this is so that classes wanting to use the same interfaces only need to implement a specific set of methods as opposed to a monolithic interface of methods.

Dependency Inversion Principle (DIP)
The DIP is all about isolating your classes from concrete implementations and having them depend on abstract classes or interfaces. It promotes the mantra of coding to an interface rather than an implementation, which increases flexibility within a system by ensuring you are not tightly coupled to one implementation.

This is about the S.O.L.I.D design principles. I hope this will you guys on the long way of design someday.

This is the first one of a series of articles. I'll be back with design patterns.

Tuesday, February 2, 2010

LINQ : Query expression vs Lambda Expression

All the time I was using LINQ on projects I was wondering whether there is a performance difference between query expression and lambda expression.

So I decided to dig into it. I wanted to examine MSIL for both of these situations. I wrote small class which has two methods. One is using query expression and the other one is using lambda.


I complied this code and got the dll and view the MSIL using ildasm.exe. This following picture will show you the MSIL of GetFirst() method.


And this following picture will show you the MSIL of the GetSecond() method.


Yes!!! you can see that there is no different between these 2 MSIL. Will there be a performance difference???

Friday, October 16, 2009


I was looking for this reCAPTCHA recently and this is what I found on my way. Hope this will help you in someway. To get an idea about reCAPTCHA watch the following video

and the following link will explain you how to implement it in your web site.


Thursday, March 26, 2009

Exit a T-SQL Cursor When Condition is met

Have you ever wanted to exit from a cursor when a condition is met? I wanted to do it. So this is how I did it.



FROM TableName

OPEN CursorName

INTO @Field1, @Field2


IF @Field1 = 1

INTO @Field1, @Field2


CLOSE CursorName

I have set my fonts to bold where you want to notice.

So that's all I hope you will get something out of it and it is true that this is not a big deal. :)

Thursday, February 5, 2009

Populate Modal popup data which is bind to a link button -

I wanted to do a POC to my client to show modal popup functionality. So I did a simple page with one Button and a TextBox. That Button is responsible to popup the modal window. On that ModalPopup I implemented a search mechanism. I used Girdview control to show the search result.

I wanted to populate the id value of that search result which was binded to a link button. This gridview and the text box and button was in a AJAX update panel control. I did this because I wanted to have the smothness of the UI.

Now I met a new problem. Because I wanted to get that value out of that LinkButton control and show it in a TextBox control which was out of the ModalPopup.

So what I did was, I just assign that LinkButton's text property to a HiddenField and I used a JavaScript function to populate that HiddenField value the TextBox.

As you all know we need a Panel control to show our ModalPopup. This is gonna be a <div> on the HTML. So I used the onblur event to call my JavaScript function.

So my problem is solved. :D

I think this will help you all one day.

Sunday, November 16, 2008

Programmatically add the META tags to an ASP.NET page

Do you want to programmatically add the META tags to an ASP.NET page? You can try to the below code:

HtmlMeta metaDesc = new HtmlMeta();
metaDesc.Name = "description";
metaDesc.Content = "Your Description goes here";

HtmlMeta metaKey = new HtmlMeta();
metaKey.Name = "keywords";
metaKey.Content = "Your keywords here";