This Angular tutorial helps you get started with Angular quickly and effectively through many practical examples.

Trending Technologies

DataBase

SQL Server

.Net Interview Question Tutorials

OOPs-Introduction
OOPs Concepts
Objects
Class
Types of Class
Regular Class
Abstract Class
Static Class
Partial Class
Sealed Class
Nested Class
Generic Class
Constructors
Constructor Introduction
Default Constructor
Parameterized Constructor
Copy Constructor
Static Constructor
Private Constructor
Constructor Overloading
Destructor
Constructor Question
OOPs Concepts
Abstraction
Encapsulation
Abstraction vs Encapsulation
Inheritance
Types of Inheritance
PolyMorphism
PolyMorphism Introduction
CompileTime PolyMorphism
RunTime PolyMorphism
Method Overloading vs Overriding
Access specifiers
Access specifiers Introduction
Default Access Modifiers Introduction
Modifier vs Access Modifiers
Loops
Loops Introduction
Continue vs Break Statement
If-Else Alternative Ways
Abstract Class & Interface
Interface Introduction
Abstract Class Introduction
Abstract Class vs Interface
When-Abstract Class and Interface
Multiple Interfaces-Same Method Name
Interface - Real Application
Interface and Abstract Class-Questions
Collections
Generics Introduction
Collections Introduction
Array vs ArrayList
Hashtable vs Dictionary
List vs Dictionary
Delegates
Delegate Introduction
Delegates and Events
Delegates Callback
Delegates Anonymous
Delegates vs Events
C# Method
Method Introduction
PassbyValue vs PassbyReference
Ref vs Out
Method-Return Multiple values
Param Keyword
Optional Parameter
Named Parameter
Extension Method
Solid Principals
SOLID Principal Introduction
SRP-(Single responsibility principle)
SRP with Multiple Methods
OCP-(Open closed principle)
LSP-(Liskov substitution principle)
ISP-(Interface segregation principle)
DIP-(Dependency inversion principle)
SOLID Principal vs Design Patterns
Garbage Collection
Garbage Collection Introduction
Dispose-Finlize
Dispose vs Finlize
Exception Handling
Exception Handling Introduction
Multiple try-catch Block
Custom Exception
Throw vs Throw ex
Finally in Real Application
Exception Handling Question
Important
This Keyword
IS vs AS
Var vs Dynamic
Object vs Dynamic
Const vs ReadOnly
Enum Keyword
Struct Keyword
Class vs Struct
== vs Equals
ToString() vs Convert.ToString()
Boxing vs Unboxing
Type Casting
Value vs Reference Types
C# String
C# StringBuilder
String vs StringBuilder
When -String and StringBuilder
String Interpolation
Yield Keyword
Performance Optimization
SQL Query Optimization
SQL Stored Procedure Optimization
.NET Core Web API Performance Optimization
.NET Projects - Technical Challenges
.NET Core- Ways to Manage Errors

SOLID principles Introduction

Prev Next

In this article we are going to discuss SOLID principles in C#. There are many blogs, articles are available on the internet regarding SOLID principles but in this particular article I will try to explain to you with as much as simple.

SOLID principles Introduction

The SOLID principles are a set of five design principles intended to make software designs more understandable, flexible, and maintainable. They were introduced by Robert C.Martin(Uncle Bob) and are widely regarded as best practices for object-oriented software design.

SOLID is an acronym for the following:

S stands for SRP (Single responsibility principle
O stands for OCP (Open closed principle)
L stands for LSP (Liskov substitution principle)
I stands for ISP (Interface segregation principle)
D stands for DIP (Dependency inversion principle)

Why need SOLID Principals?

Developers build applications with good and tidy designs using their knowledge and experience. But over time, applications might develop bugs. The application design must be altered for every change request or new feature request. After some time, we might need to put in a lot of effort, even for simple tasks, and it might require a full working knowledge of the entire system. But we can't blame change or new feature requests. They are part of software development. We can't stop them or refuse them either. So who is the culprit here? It is the design of the application.

So we need to Choose the correct Design Patterns to build the software based on its specifications. We go through the Design Principles like SOLID Pricipals.

Advantage of SOLID Principals

It reduces the dependencies so that a block of code can be changed without affecting the other code blocks.
The principles intended to make design easier, understandable.
By using the principles, the system is maintainable, testable, scalable, and reusable.
It avoids the bad design of the software.

Disadvantages of SOLID Principles in C#

SOLID principles can result in a more complex codebase because they demand breaking code into smaller, more focused classes and interfaces.
Following SOLID principles may result in the creation of more classes and interfaces, making the codebase more difficult to browse.
It could take some time for developers to understand and successfully apply the concepts.

Prev Next

.Net Interview Question Tutorials

SOLID principles Introduction

Top Articles