December 2010 Blog Posts
- Abstract SQL
ADO.NET Sql classes wrapper; provides a clean fluent interface library that allows you to write very concise code and avoid the repetitiveness of ADO.NET. It can be used in all types of applications, even supports CLR stored procedures. It is written in C# 2.0.
- Gridify for ASP .NET MVC
Easy solution for grids on top of ASP.NET MVC
Make grids from your data tables in a really lightweight manner! How lightweight? Well, exactly TWO line changes. You don't have to add new action parameters or anything. Really simple!
- Paypal adaptive payments using .Net (C#)
This is a...
The Interface Segregation Principle (ISP) is another principle about OOD.
It simply states that:
“CLIENTS SHOULD NOT BE FORCED TO DEPEND UPON INTERFACES
THAT THEY DON’T USE”
If we return back to the first OOD principle, the Single Responsibility Principle, it can be said that this principle should also apply to interfaces or to abstract class, in addition to the concrete classes.
Therefore, one interface should mean one responsibility, without creating the so-called “fat interfaces”, i.e. interfaces that contain too many methods/properties that relate to more than 1 responsibility.
To find an example of violation of this principle does not need to go too far,...
The Liskov Substitution Principle (LSP) is another principle that has to do with software design and namely with inheritance.
This principle takes its name from Barbara Liskov, U.S. scientist in computer science.
This principle simply states that
“CLASSES THAT USE REFERENCES TO BASE CLASSES MUST BE ABLE TO USE OBJECTS OF DERIVED CLASSES WITHOUT KNOWING IT"
In other words, if we have a class (say Class C) that use a reference to a base class inside (Class B), then Class C MUST be able to use a reference with ANY derivate class of Class B (present and future), without knowing it and especially...