Skip to main content

Software Principles Using C#

 

 


Software Principles Using C# by Ziggy Rafiq

Software Principles Using C#

There are several software principles commonly used in C# development, which are as follows.

  • SOLID Principles: The SOLID principles are a set of five principles that guide the design of software systems. They include the Single Responsibility Principle (SRP), Open-Closed Principle (OCP), Liskov Substitution Principle (LSP), Interface Segregation Principle (ISP), and Dependency Inversion Principle (DIP).
  • KISS Principle: The KISS (Keep It Simple, Stupid) principle states that software systems should be simple and straightforward, without unnecessary complexity.
  • YAGNI Principle: The YAGNI (You Ain't Gonna Need It) principle states that developers should only add functionality when it is actually needed, instead of adding it in anticipation of future needs.
  • DRY Principle: The DRY (Don't Repeat Yourself) principle states that developers should aim to write reusable code and avoid repetition.
  • Separation of Concerns (SOC): The Separation of Concerns principle states that different parts of a software system should be separated into distinct, independent components that are focused on solving specific problems.
  • Law of Demeter (LOD): The Law of Demeter states that an object should only communicate with its immediate neighbours and not know the inner workings of other objects.

By following these software principles, developers can write maintainable, reusable code, and are less prone to bugs and errors. This can reduce the amount of time and effort required to develop and maintain a software system and can make it easier to add new features in the future.

I will upload code samples for Software Principles Using C# on the following URL Address on my GitHub Repository. (Currently, it is not available ) https://github.com/ziggyrafiq/Software-Principles-using-C-Sharp and I will be writing blog posts on DRY Principle

 



Labels:

Comments

Post a Comment

Most Viewed Ziggy Rafiq Blog Posts

A Complete Guide to Using GUIDs in C# with Code Examples

  Overview In this post, we are looking at GUIDs (Globally Unique Identifiers), which are widely used in C# for generating unique identifiers for objects, entities, and resources in a system. In this post, we'll explore the basics of GUIDs in C#, their advantages, and how to convert strings to GUIDs. In this post, we have used Guid Generator to create the GUID from the following URL Address https://guidgenerator.com/ What is GUID GUID (Globally Unique Identifier) in C# is a 128-bit value that is used to identify objects, entities, or resources in a unique manner across different systems and applications. It is also known as UUID (Universally Unique Identifier) in some other programming languages.   GUIDs are generated using a combination of unique factors such as the MAC address of the network adapter, the current time and date, and a random number. The resulting GUID is a string of 32 hexadecimal digits separated by hyphens, such as "b86f2096-237a-4059-8329-1bbcea72769b...
Post a Comment
Read more

How to Truncate String in C#

  Overview In today’s post, I am writing about one of the fundamental aspects of C# and as programmers, we should use this approach I have realised throughout my life as a software engineer that not everyone knows the most basic approaches or how to use them efficiently. Truncating a string in C# means reducing the length of a string to a specified number of characters, typically by removing characters from the end of the string. This is often done when a string is too long to be displayed or used in a specific context and needs to be shortened to fit. Ley says if we have a string that is 100 characters long, but we only want to display the first 50 characters, we will truncate the string to a length of 50. There are several ways to truncate a string in C#, including using the Substring method, StringBuilder, and LINQ. A simple example of this is below, we're creating a longString variable with a long string value. We're also defining a maxLength variable with a value of 20...
Post a Comment
Read more

ASP.net Core Services Lifetime Differences Between Using AddTransient, AddScoped and AddSingleton Services

  ASP.net Core Services Lifetime Differences Between Using AddTransient, AddScoped and AddSingleton Services Overview In this blog post, I will be explaining to you the ASP.net core Service Lifetime and will be explaining to you what is the difference between them and which one can be a risk to a memory leak if used incorrectly. AddTransient, AddScoped, and AddSingleton are dependency injection services in ASP.NET Core. The differences between them are as follows below. AddTransient: A new instance of the service is created every time it is requested. AddScoped: A single instance of the service is created per request within the same scope. AddSingleton: A single instance of the service is created for the entire application lifetime. In general, it's recommended to use AddScoped for services that are stateful and AddTransient for services that are stateless or have a short lifetime. AddSingleton is usually used for services that are expensive to create or only need to be crea...
Post a Comment
Read more