Discover and read the best of Twitter Threads about #dotnet

Clean Architecture Solution Layers in .NET

Clean architecture is an architecture that follows set of design principles (mostly SOLID) and divides the solution into different layers (mostly 4 layers).

- Domain
- Application
- Infrastructure
- Presentation 🧵 ⬇️
#dotnet

Domain : It contains core business entities and domain logics

Application :Responsible for communicating with domain and handle use cases.

Infrastructure layer contains implementations of external services and interfaces for example logging or repositories.
#dotnet

Presentation is related to user interface (UI) part and we deal with things that are visible to users e.g. (Razor Pages or F.E Angular/React)

If you like it you would be interested in my weekly .NET newsletter as well.
Join with 2800+ here : buff.ly/3pCmHQk

#dotnet

Read 3 tweets

What is the difference b/w field and property , what are the different types of properties in C# ?

- Properties
- Field vs Properties
- 6 Types of Properties

#dotnet

Properties vs Field

- 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

#dotnet

Read 8 tweets

Adapter Design Pattern - Simplifed💡

Definition:

The adapter pattern converts the interface of a class into another interface clients expect. The adapter lets classes work together that couldn’t otherwise because of incompatible interfaces.

#Dotnet

Real-Wolrd Analogy:

• Stefan from Serbia arrived in the UK.
• Stefan has a classic EU charger with a two-part outlet.
• The UK has a standard three-part plug.

How will Stefan charge his phone?

Answer: By using an adapter.

The adapter creates the possibility of connecting two different interfaces
(2 plugs).
It gets one type of input and produces a different type of output.

How to increase productivity?

5 Visual Studio Refactoring Tips 💡

If we use 𝐕𝐢𝐬𝐮𝐚𝐥 𝐒𝐭𝐮𝐝𝐢𝐨 as an 𝐈𝐃𝐄, it can help us a lot to quickly and successfully refactor the code.

Visual Studio makes things easy for us and has support for a lot of code changes.

#Dotnet

• 𝐑𝐞𝐧𝐚𝐦𝐢𝐧𝐠 𝐢𝐝𝐞𝐧𝐭𝐢𝐟𝐢𝐞𝐫

Use 𝐂𝐭𝐫𝐥+𝐑, 𝐑 - when you change the name of a variable in one place, all references are automatically changed.

• 𝐄𝐱𝐭𝐫𝐚𝐜𝐭 𝐌𝐞𝐭𝐡𝐨𝐝

The hotkey 𝐂𝐭𝐫𝐥+. triggers the 𝐐𝐮𝐢𝐜𝐤 𝐀𝐜𝐭𝐢𝐨𝐧𝐬 𝐚𝐧𝐝 𝐑𝐞𝐟𝐚𝐜𝐭𝐨𝐫𝐢𝐧𝐠𝐬 menu. From this menu, we can choose 𝐄𝐱𝐭𝐫𝐚𝐜𝐭 𝐌𝐞𝐭𝐡𝐨𝐝 or 𝐄𝐱𝐭𝐫𝐚𝐜𝐭 𝐋𝐨𝐜𝐚𝐥 𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧 𝐄𝐱𝐭𝐫𝐚𝐜𝐭 𝐋𝐨𝐜𝐚𝐥 𝐅𝐮𝐧𝐜𝐭𝐢𝐨𝐧.

Read 6 tweets

I almost started working on a new project. 🚀

These are the 4 steps I follow before coding: 🧵

#Dotnet

1. Requirements Gathering

I try to have a deep understanding of project goals, functionality, and user expectations. Therefore, I believe that clear communication at this stage lays the foundation for a successful outcome.

2. Software Architecture

I carefully create the pieces of the software architecture. I analyze all client requirements and consider factors such as scalability, performance, security, and maintainability. I do this together with the client.

Read 6 tweets

C# | .Net Tip 💡

𝐇𝐨𝐰 𝐭𝐨 𝐢𝐧𝐜𝐫𝐞𝐚𝐬𝐞 𝐭𝐡𝐞 𝐫𝐞𝐚𝐝𝐚𝐛𝐢𝐥𝐢𝐭𝐲 𝐨𝐟 𝐲𝐨𝐮𝐫 𝐜𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐚𝐭𝐢𝐨𝐧 𝐜𝐨𝐝𝐞?

I'm sure everyone reading this post has heard of 𝐞𝐱𝐭𝐞𝐧𝐬𝐢𝐨𝐧 𝐦𝐞𝐭𝐡𝐨𝐝𝐬. 🧵

Good practice at the end of the post. 👌

#Dotnet

When creating an application, the first thing we do is configure it.

We configure: logging, connect the database with ORM, and configure CORS.
We define the method of authentication, DI services, and various bindings.

When we write all this code in the 𝐂𝐨𝐧𝐟𝐢𝐠𝐮𝐫𝐞𝐒𝐞𝐫𝐯𝐢𝐜𝐞𝐬 𝐦𝐞𝐭𝐡𝐨𝐝 𝐢𝐧 𝐏𝐫𝐨𝐠𝐫𝐚𝐦.𝐜𝐬, everything gets messy. These methods can reach over 500 lines of configuration code.
Changing something is very difficult to navigate.

Read 9 tweets

💡𝐃𝐨𝐧’𝐭 𝐑𝐞𝐩𝐞𝐚𝐭 𝐘𝐨𝐮𝐫𝐬𝐞𝐥𝐟 (𝐃𝐑𝐘) 𝐏𝐫𝐢𝐧𝐜𝐢𝐩𝐥𝐞

It states that don’t repeat yourself what it means it is saying don’t duplicate code , avoid duplication. Purpose is to reduce the redundant code in your application 🧵⏬
#dotnet

Following the DRY Principle can give us following benefits

1. Improved maintainability of code

2. Reduces the risks of bugs

3. Code becomes easier to understand

#dotnet

If you are not applying DRY Principle you need to test/debug all process separately for similar code.

We can fulfil DRY Principle using Inheritance and Polymorphism.

#dotnet

Mukesh Murugan

@iammukeshm

🚀 Backend Developer Roadmap for .NET Developers. (2023 Edition)

Follow this thread along for the entire roadmap.

#dotnet #developer #backend

Step 0: Know your basics.
Be familiar with OOPS, Brush up your problem solving skills, and learn GIT.
#dotnet #developer #backend

Next, get your C# skills right to the latest changes. #dotnet #developer #backend #csharp

Read 23 tweets

💡 NULL Operators Guide in C#

- Ternary Operator (? :)

- Null Forgiving Operator (!.)

- Null Conditional Operator (?.)

- Null Coalescing Operator (??)

- Null Coalescing Assignment Operator (??=) 🧵⏬

#dotnet

Ternary Operator or Conditional Operator(?.) is used to evaluate a condition and then we can do something on that basis for true and false

#dotnet

Null Forgiving or Null Suppression Operator (!.) is used to suppress all nullable warnings for preceding expression. It has no effect on runtime

#dotnet

Milan Jovanović

@mjovanovictech

What is the required keyword in C#?

It was added in C# 11.

When creating a new object instance, you can use the required keyword to indicate that a field or property must be initialized.

Have you used the C# required keyword already?

#dotnet

If you try to create a new object instance and don't assign a value to a required property, you'll get a compile error.

Before this, you had to use constructors with all the required values as parameters.

Now you can also work with object initializers and not worry about members not having a value assigned.

In combination with nullable reference types, you can create a robust design.

Read 4 tweets

💡HTTP Client Class in C#

. Introduction
Methods
Properties
Dependency injection 🧵⏬

#dotnet

HttpClient is a class in C# that is used for making HTTP calls of different kinds (most commonly Get/Put/Delete/Post).This class comes from namespace System.Net.Http

Most commonly used methods of this class are
- GetAsync
- DeleteAsync
- PostAsync
- PutAsync
- Dispose

#dotnet

💡 15+ .NET Libraries you should Know

Now a days libraries play an important role in your development, start learning these libraries for a good development experience.

- Mediator for CQRS
- Dapper for micro-ORM

See more🧵⏬
#dotnet

- Serilog and NLog for logging

- Bogus for fake data generation

- Fluent Validation for validations

- SignalR for real time communication

- Moq for mock interfaces and classes

- Hangfire and Quartz for background jobs

- Noda Time best in the town for date-time

#dotnet

- Autofac for Dependency Injection Container

- MiniProfiler for profiling your application

- Automapper, Mapster and Mapperley for Mappings

- Polly for fault handling (Retry, Circuit Break)

#dotnet

Steve "ardalis" Smith

@ardalis

Clean architecture aka ports and adapters is simply an approach to building systems that follow DIP. That is, depend on abstractions not implementations, and make sure those abstractions don’t depend on details.
#dotnet #cleanarchitecture

It doesn’t make exceptions for different kinds of implementations. It doesn’t exclude web services or email sending or file system access. Why would it be inconsistent about persistence or ORM usage?

If you find it useful to bypass using an abstraction (you control) in favor of relying directly on an implementation detail, go ahead and do so! Your app will still work! But the first law of architecture is everything is a trade off so just understand the pros and cons.

Read 4 tweets

💡IEnumerable vs IQueryAble in .NET

1) Whatis IEnumerable
2) What is IQueryAble
3) Difference b/w them ⏬

#csharp #dotnet

IEnumerable and IQueryable interfaces are both used to work with collections of data and both support LINQ (Language Integrated Query)
#dotnet

𝐈𝐐𝐮𝐞𝐫𝐲𝐚𝐛𝐥𝐞

✅ IQueryable executes queries on the server side.

✅ It is designed specifically to work with LINQ

✅ It extends IEnumerable, which means it includes all of the functionality of IEnumerable.
#dotnet

💡Tracking vs Non Tracking Queries in .NET
1) Tracking Queries
2) Non Tracking Queries
3) Identity Resolution
4) How to set tracking by default for context🧵🔽
#dotnet

𝐓𝐫𝐚𝐜𝐤𝐢𝐧𝐠 : By default all queries are tracked , so behind the seen a change tracker keeps working on each entity. If you want to perform Update/Delete then you should use tracking.
#dotnet

𝐍𝐨𝐧 𝐓𝐫𝐚𝐜𝐤𝐢𝐧𝐠 : If you just need read only data then you don't need your queries to keep tracking of change , you can simply go with no tracking and help the query run more speedy.
#dotnet

💡Global Error Handling in .NET ?
1) Why we need it
2) Pros and cons
3) Code implementation🧵🔽

#dotnet

While working with .NET application we sometime come up with exception and we can deal with it in two ways , either by using try catch block in each class (controller level or service level) or we can define a centralized and global point to catch the exception.
#dotnet

♉ Pros of using Global Exception

1. It provides us a centralized error handling point and makes easier for us to manage.

2. Code readability is improved as we get rid of writing try-catch code in each method
#dotnet

💡 Life of Query in EF

𝐒𝐭𝐞𝐩 𝟏 : The LINQ Query is processed by EF Core and build an representation that is processed by database provider, and the result is cached later on so we don't need to process it every time #dotnet

See thread 🧵⏬

𝐒𝐭𝐞𝐩 𝟐 : The result is passed to the db provider and db provider identifies which parts of query can be evaluated in db, these parts are then translated into query language (e.g. SQL) after that translated query is sent to db and db returns results (but not entity instances)

𝐒𝐭𝐞𝐩 𝟑 : For each item we check if it is tracking query EF checks the data in existing change tracker if found relevant entity is returned else new is created, its change tracking get set up and it is returned

For non tracking a new entity is always created and returned.

💡 7 Tips to write better LINQ Queries

𝐔𝐬𝐞 𝐨𝐟 𝐀𝐬𝐍𝐨𝐓𝐫𝐚𝐜𝐤𝐢𝐧𝐠 : For read only queries e.g. (GetAll,GetById etc.) use AsNoTracking , when we use it entities are not tracked for change so it brings data more speedily. #dotnet

See thread 🧵🔽

𝐈𝐧𝐜𝐥𝐮𝐝𝐞 𝐧𝐞𝐜𝐞𝐬𝐬𝐚𝐫𝐲 𝐄𝐧𝐭𝐢𝐭𝐢𝐞𝐬 𝐚𝐧𝐝 𝐂𝐨𝐥𝐮𝐦𝐧𝐬 : While retrieving data from multiple table make sure to include only necessary tables and columns Use eager loading only when it is necessary.
#dotnet

𝐅𝐨𝐫 𝐥𝐚𝐫𝐠𝐞 𝐝𝐚𝐭𝐚 𝐮𝐬𝐞 𝐒𝐤𝐢𝐩 𝐚𝐧𝐝 𝐓𝐚𝐤𝐞 : Use skip and take to retrieve data from table for large collections because if we try to bring all data in single try it can take time that will give bad user experience takes next values.
#dotnet

Read 8 tweets

💡 How to store Password in Database

Three common practices that are used for passwords, but first two has some serious issues.

✔️ Plain text password
✔️ Hashed password
✔️ Hashed password with Salt
✔️What is Salt
✔️How to validated hash password

#dotnet

#csharp #dotnet

1️⃣ Plain Text Password
Saving password in plain text is the worst approach because it is open to everyone who has database access and an easy target for attackers. Its not recommended at all.

2️⃣ Hashed Password
Hashing the plain text password first and then saving it, it seems safe but it isn’t safe again, you can fall for attack in this case as well rainbow attack.