Hello I’m Sina Riyahi

What is pattern matching?

• C#
• June, 10, 2024
• 10 min

💡Pattern matching is the process of taking an expression and testing whether it matches certain criteria, such as ‘being a specified type’ or ‘matching a specified constant value’.

🔦Common to all patterns is the Boolean match/no-match characteristic, so, the specified expression either matches the pattern or it does not. Pattern matching is a check and so can be used when branching code.

Advantages of Using Pattern Matching in C#

🔎Enhanced readability. ✏️Reduction in lines of code. 🚀Improved maintainability. ⏳️More ways to express your algorithms.

𝗖# 𝟭𝟮 introduces 𝗽𝗿𝗶𝗺𝗮𝗿𝘆 𝗰𝗼𝗻𝘀𝘁𝗿𝘂𝗰𝘁𝗼𝗿𝘀, a concise syntax to declare constructors whose parameters are available anywhere in the body of the type.

• C# 12
• June, 25, 2024
• 10 min

𝗧𝗵𝗲 𝗺𝗼𝘀𝘁 𝗰𝗼𝗺𝗺𝗼𝗻 𝘂𝘀𝗲𝘀 𝗳𝗼𝗿 𝗮 𝗽𝗿𝗶𝗺𝗮𝗿𝘆 𝗰𝗼𝗻𝘀𝘁𝗿𝘂𝗰𝘁𝗼𝗿 𝗽𝗮𝗿𝗮𝗺𝗲𝘁𝗲𝗿 𝗮𝗿𝗲: ◾ As an argument to a base() constructor invocation. ◾ To initialize a member field or property. ◾ Referencing the constructor parameter in an instance member.

🔥Primary constructors is a new feature of C# 12 that allows us to declare parameters in a class or struct declaration that their scope is the entire class (or struct). It is important to understand the distinction between parameters and fields.

Lorem ipsum dolor sit amet consectetur adipisicing elit. Quod ex dolorum aut accusantium, fugit sunt vero animi quos porro excepturi. Quia delectus nulla voluptatem unde incidunt. Magnam natus officiis saepe.

💡 which simplifies the syntax for initializing properties in classes. This feature enhances code readability and reduces boilerplate code, making C# development more efficient.

𝗨𝘀𝗲 𝗻𝗮𝗺𝗲𝗼𝗳() 𝘁𝗼 𝗰𝗼𝗻𝘃𝗲𝗿𝘁 𝗮𝗻 𝗲𝗻𝘂𝗺 𝘁𝗼 𝗮 𝘀𝘁𝗿𝗶𝗻𝗴

• C#
• June, 01, 2024
• 10 min

🐢ToString() method. Types commonly override the Object. ToString method to return a string that represents the object instance. For example, the base types such as Char, Int32, and String provide ToString implementations that return the string form of the value that the object represents.

🐇The nameof operator in C# is a simple yet powerful feature that enhances code maintainability and reduces the likelihood of errors, particularly in scenarios involving reflection, logging, and data validation. By dynamically obtaining names as strings at compile time, nameof promotes cleaner and more robust code.

🚀 𝗻𝗮𝗺𝗲𝗼𝗳() is the preferred way to convert an enum to a string. This is because nameof() is evaluated at compile time and will inject a string literal that will never change, while ToString() is evaluated at runtime. This means that nameof() is more efficient and can help to improve the performance of your code.

💡 Using 𝗻𝗮𝗺𝗲𝗼𝗳() with enums can lead to mismatched enum member names if the enum changes without recompiling referencing projects, as nameof() provides names at compile-time.

JSON (JavaScript Object Notation) is a lightweight format for data exchange. There are several libraries available to work with JSON

• C#
• June, 15, 2024
• 10 min

👍 𝗡𝗲𝘄𝘁𝗼𝗻𝘀𝗼𝗳𝘁.𝗝𝘀𝗼𝗻, also known as Json.NET, the most popular JSON library. It’s Feature-rich, ideal for complex scenarios.

😍 𝗦𝘆𝘀𝘁𝗲𝗺.𝗧𝗲𝘅𝘁.𝗝𝘀𝗼𝗻 is a built-in JSON library. It’s fast and doesn’t use much computer memory. It’s perfect for modern .NET applications.

👑 𝗡𝗲𝘁𝗝𝗦𝗢𝗡 is a lightweight JSON library. It’s faster than both Newtonsoft.Json and System.Text.Json. It’s not as widely known as other JSON libraries.

𝗘𝗙 𝗖𝗼𝗿𝗲 𝟳 𝗕𝘂𝗹𝗸 𝗗𝗲𝗹𝗲𝘁𝗲

• EF Core
• June, 30, 2024
• 10 min

🐢 𝗕𝗲𝗳𝗼𝗿𝗲 EF Core 7, deleting data involved looping through entities, marking them for removal, and finally saving changes. This approach translates to multiple database roundtrips, impacting performance, especially for large datasets.

SaveChanges when you have to delete multiple entities. To perform a bulk delete, you need to call the method with the list of entities you want to delete.

🔥EF Core 𝗕𝘂𝗹𝗸 𝗗𝗲𝗹𝗲𝘁𝗲 offers a significant performance improvement for deleting large datasets in your applications.

𝗥𝗲𝘁𝘂𝗿𝗻 𝗮𝗻 𝗲𝗺𝗽𝘁𝘆 𝗰𝗼𝗹𝗹𝗲𝗰𝘁𝗶𝗼𝗻 𝗶𝗻𝘀𝘁𝗲𝗮𝗱 𝗼𝗳 𝗻𝘂𝗹𝗹

• C#
• June, 8, 2024
• 10 min

✅ it is a recommended practice to 𝗿𝗲𝘁𝘂𝗿𝗻 𝗲𝗺𝗽𝘁𝘆 𝗰𝗼𝗹𝗹𝗲𝗰𝘁𝗶𝗼𝗻𝘀 instead of null when dealing with methods or properties that return collections such as lists, arrays, dictionaries, etc. The primary reason for this is to avoid potential null reference exceptions and simplify the client code that consumes these collections.

❌ When a method 𝗿𝗲𝘁𝘂𝗿𝗻𝘀 𝗻𝘂𝗹𝗹, the caller needs to explicitly check for null before performing any operations on the returned collection. This additional null check can clutter the client code and potentially lead to null reference exceptions if it is overlooked.

🔥 On the other hand, returning an empty collection ensures that the client code can safely iterate over the collection without worrying about null checks. An empty collection is an object, albeit an empty one, and can be safely used for various operations without any risk of null reference exceptions.

💡𝗖𝗼𝗺𝗺𝗼𝗻 𝗲𝗺𝗽𝘁𝘆 𝗰𝗼𝗹𝗹𝗲𝗰𝘁𝗶𝗼𝗻 𝗶𝗻𝗶𝘁𝗶𝗮𝗹𝗶𝘇𝗮𝘁𝗶𝗼𝗻𝘀 𝗶𝗻 𝗖#: ◾For lists: 𝗿𝗲𝘁𝘂𝗿𝗻 𝗻𝗲𝘄 𝗟𝗶𝘀𝘁<𝗧>(); ◾For arrays: 𝗿𝗲𝘁𝘂𝗿𝗻 𝗻𝗲𝘄 𝗧[𝟬]; ◾For dictionaries: 𝗿𝗲𝘁𝘂𝗿𝗻 𝗻𝗲𝘄 𝗗𝗶𝗰𝘁𝗶𝗼𝗻𝗮𝗿𝘆<𝗧𝗞𝗲𝘆, 𝗧𝗩𝗮𝗹𝘂𝗲>(); ◾For sets: 𝗿𝗲𝘁𝘂𝗿𝗻 𝗻𝗲𝘄 𝗛𝗮𝘀𝗵𝗦𝗲𝘁<𝗧>(); ◾For enumerable: 𝗿𝗲𝘁𝘂𝗿𝗻 𝗘𝗻𝘂𝗺𝗲𝗿𝗮𝗯𝗹𝗲.𝗘𝗺𝗽𝘁𝘆<𝗧>();

Returning null or an Empty Collection. When returning an array or collection, you must indicate that there are zero items by returning either null or a collection instance with no items. The better choice, in general, is to return a collection instance with no items.