It is software assembled into an app pipeline to handle requests and responses. In simple, it gives us the facility to add additional logic before and after the HTTP request.
What is SOLID , why we need these principles and S explained ?
It is combination of 5 design principles
S - Single Responsibility Principle (SRP)
O - Open/Closed Principle (ORP)
L - Liskov Substitution Principle (LSP)
I - Interface Segregation Principle (ISP)
Thread ๐งต๐
D - Dependency Inversion Principle (DIP)
Why we need SOLID or its benefits
- Better Testability
- Reduces coupling
- Removes Duplication
- Increases Readability
- Increases Extensibility
SRP says :-
- A class/method should have one reason to change
- A class/method should have only one responsibility
- A class/method should be related to a single purpose
With SRP we achieve :-
- Class/method becomes smaller and cleaner
- Now in future updating the code becomes easier
4) TimeZoneInfo, used in .NET, relies on Windows time zone IDs, which may differ from widely used Olson (tz) identifiers
5) Unfortunately humanity didโ not agree on single calendar (Gregorian, Julian, Coptic and Buddhist) , NodaTime covers this space which default lacks
๐Read these 15 awesome topics of .NET via my Newsletter.
Join 3400+ : for upcoming issues.
EP 14: 7 Awesome Features of C# (10)
EP 13: Bogus - A Fake Data Generation
EP 12: Global Exception Handling
EP 11: Default vs Autofac DI Container
EP 10: Actionโฆ https://t.co/62ug4BOMVBlnkd.in/dNHxJGRG twitter.com/i/web/status/1โฆ
- Properties are first class citizens in C#
- We used properties to achieve abstraction
- Properties are implemented via accessors
- Enable developers to write code that accurately expresses their design intent #dotnet
Read only Properties
- Serve the purpose of getters
- Use them for retrieving the information in DTO
- We can not set them