AMJED Chahoumi

All() vs. TrueForAll() in .NET When working with collections in .NET, developers often come across All() and TrueForAll(). Both check if all elements in a collection meet a condition, but they aren’t exactly the same. All() - Comes from LINQ and works on any IEnumerable<T>. - Uses deferred execution and integrates with queries. - Great when flexibility across collections is needed. TrueForAll() - Defined on List<T> and limited to that type only. - Executes immediately when the check is made. - Slightly faster when working only with lists. Rule of thumb: - Use All() for versatility across collections. - Use TrueForAll() for performance with List<T>. 👉 Want to learn more? Swipe ——— 🔔 Follow Asim Noor for more .NET insights! ♻️ Repost to help your network!

172

12 Kommentare

𝗕𝗲𝘀𝘁 .𝗡𝗘𝗧 𝗧𝗼𝗼𝗹𝘀 & 𝗣𝗮𝗰𝗸𝗮𝗴𝗲𝘀 𝗘𝘃𝗲𝗿𝘆 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗦𝗵𝗼𝘂𝗹𝗱 𝗞𝗻𝗼𝘄! The .NET ecosystem is huge, and choosing the right tools can save you 𝘁𝗶𝗺𝗲, 𝗲𝗳𝗳𝗼𝗿𝘁, 𝗮𝗻𝗱 𝗵𝗲𝗮𝗱𝗮𝗰𝗵𝗲𝘀. That’s why I have created this list of the 𝗺𝗼𝘀𝘁 𝗽𝗼𝗽𝘂𝗹𝗮𝗿 𝗮𝗻𝗱 𝘂𝘀𝗲𝗳𝘂𝗹 .𝗡𝗘𝗧 𝘁𝗼𝗼𝗹𝘀 & 𝗹𝗶𝗯𝗿𝗮𝗿𝗶𝗲𝘀 across different categories: 🔐 𝗔𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗶𝗼𝗻 – JWT, IdentityServer, OpenIddict, Duende, Ocelot, OAuth 🗄️ 𝗢𝗥𝗠 – EF Core, Dapper, NHibernate, Marten, OrmLite, PetaPoco 🧪 𝗧𝗲𝘀𝘁𝗶𝗻𝗴 – xUnit, NUnit, MSTest, FluentAssertions, Moq, Bogus 📜 𝗟𝗼𝗴𝗴𝗶𝗻𝗴 – Serilog, NLog, log4net, Elastic APM, Seq, Splunk ⚙️ 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺𝘀 – ASP.NET Core, Blazor, MAUI, Xamarin, Orleans, gRPC ⏳ 𝗕𝗮𝗰𝗸𝗴𝗿𝗼𝘂𝗻𝗱 𝗣𝗿𝗼𝗰𝗲𝘀𝘀𝗶𝗻𝗴 – Hangfire, Quartz.NET, MassTransit, RabbitMQ, Azure Service Bus, MediatR 📊 𝗥𝗲𝗽𝗼𝗿𝘁𝗶𝗻𝗴 – DinkToPdf, QuestPDF, iText7, DevExpress, SyncFusion, Stimulsoft 🎨 𝗙𝗿𝗼𝗻𝘁𝗲𝗻𝗱 𝗨𝗜 – MudBlazor, Blazorise, Radzen, Syncfusion UI, Telerik UI, LiveCharts2 💡 These tools are not just “nice-to-have” — they are the 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗯𝗹𝗼𝗰𝗸𝘀 behind modern, scalable, and maintainable .NET applications. 👉 Which ones are your go-to in real projects? 👉 Any favorites I missed that you think should be on the list? 𝗡𝗼𝘁𝗲: Some tools in this list may overlap categories. For example:  • MediatR → not a scheduler like Hangfire/Quartz, but often used for in-process workflows (notifications, commands, async operations).  • gRPC → technically a framework/protocol, but I grouped it under Platforms for simplicity.  • Ocelot → commonly used as an API Gateway in .NET microservices. 👉 The intention of this list is not strict classification, but to highlight the most useful and widely adopted tools that real projects rely on. #dotnet #csharp #programming #developers #softwareengineering

973

27 Kommentare

🚀 𝐖𝐡𝐚𝐭’𝐬 𝐭𝐡𝐞 𝐃𝐢𝐟𝐟𝐞𝐫𝐞𝐧𝐜𝐞 𝐁𝐞𝐭𝐰𝐞𝐞𝐧 ‘𝐔𝐬𝐞’, ‘𝐌𝐚𝐩’, 𝐚𝐧𝐝 ‘𝐑𝐮𝐧’ 𝐢𝐧 𝐀𝐒𝐏.𝐍𝐄𝐓 𝐂𝐨𝐫𝐞 𝐌𝐢𝐝𝐝𝐥𝐞𝐰𝐚𝐫𝐞? 🚀 ⁉️ 𝐄𝐯𝐞𝐫 𝐛𝐞𝐞𝐧 𝐜𝐨𝐧𝐟𝐮𝐬𝐞𝐝 𝐚𝐛𝐨𝐮𝐭 𝐰𝐡𝐞𝐧 𝐭𝐨 𝐜𝐡𝐨𝐨𝐬𝐞 𝐔𝐬𝐞, 𝐌𝐚𝐩, 𝐨𝐫 𝐑𝐮𝐧 𝐢𝐧 𝐀𝐒𝐏.𝐍𝐄𝐓 𝐂𝐨𝐫𝐞? Let’s break it down in a clear and simple way 👇 🧱 𝑾𝒉𝒂𝒕 𝒊𝒔 𝑴𝒊𝒅𝒅𝒍𝒆𝒘𝒂𝒓𝒆? In ASP.NET Core, middleware is a component that handles HTTP requests and responses. Each component can: Decide whether to pass the request to the next component in the pipeline. Perform actions before and/or after the next component executes. ⚙️ 𝑾𝒉𝒂𝒕 𝑨𝒓𝒆 𝑹𝒆𝒒𝒖𝒆𝒔𝒕 𝑫𝒆𝒍𝒆𝒈𝒂𝒕𝒆𝒔? Request delegates process HTTP requests and they’re configured using Use, Map, and Run. Here’s how they differ: 🔁 𝐔𝐬𝐞 – 𝐂𝐡𝐚𝐢𝐧 Use lets you chain multiple delegates together. You get a next parameter, and you can choose whether to call it or not. ✅ If you skip next(), the pipeline ends there — this is called short-circuiting. ⛔ 𝐑𝐮𝐧 – 𝐄𝐧𝐝 𝐭𝐡𝐞 𝐏𝐢𝐩𝐞𝐥𝐢𝐧𝐞 Run is a terminal middleware. It does not receive a next parameter and stops the pipeline when called. A̳n̳y̳ ̳m̳i̳d̳d̳l̳e̳w̳a̳r̳e̳ ̳r̳e̳g̳i̳s̳t̳e̳r̳e̳d̳ ̳a̳f̳t̳e̳r̳ ̳R̳u̳n̳ ̳w̳i̳l̳l̳ ̳n̳o̳t̳ ̳b̳e̳ ̳e̳x̳e̳c̳u̳t̳e̳d̳.̳ 🌳 𝐌𝐚𝐩 – 𝐁𝐫𝐚𝐧𝐜𝐡 𝐭𝐡𝐞 𝐏𝐢𝐩𝐞𝐥𝐢𝐧𝐞 If you need to branch the pipeline, you can use Map. What is branching?  It is used like a convention. For instance, if the request path starts with the given path, the branch is executed.   This is great for modularizing your app and handling specific routes differently. 💬 Which one do you use most often? And did you learn something new today? Let’s discuss in the comments 👇 #dotnet #aspnetcore #middleware #csharp #backend #webdevelopment #programming

177

25 Kommentare

Deadlock in Async Programming — Why it can still happen with async/await? Many developers assume that using async/await guarantees immunity from deadlocks. Unfortunately, that’s not always true — especially in UI applications (WinForms, WPF) or the legacy ASP.NET SynchronizationContext. The Problem: The most common mistake is calling an async method synchronously, like this: var result = GetDataAsync().Result; // or .Wait() What happens behind the scenes: The UI or request thread blocks, waiting for the async call to complete. The async method tries to resume on the same thread/context after the await. That thread is already blocked → Deadlock! The Solution Always use await instead of .Result or .Wait(). For library or non-UI code: var result = await GetDataAsync().ConfigureAwait(false); This prevents context capture, avoids deadlocks, and often improves performance. Pro Tips: In ASP.NET Core, there’s no SynchronizationContext by default → fewer deadlocks. In UI apps, never block the UI thread — keep async flow end-to-end. Use ConfigureAwait(false) consistently in reusable libraries. Have you ever run into a deadlock caused by Task.Result or Wait() in your projects? How did you solve it? #DotNet #CSharp #AsyncProgramming #Deadlock #Concurrency #Multithreading #SoftwareDevelopment #CodingBestPractices

91

8 Kommentare

⚡ Boot an ASP.NET Core app inside your tests ⚠️ The Problem Many teams spin up containers or rely on shared servers for integration tests. That slows tests down, adds flakiness, and requires infrastructure. ✅ The Solution Subclass WebApplicationFactory to create a reusable Test Application instead of using the WebApplicationFactory directly. This allows you to pack shared configuration and features in the Test Application, making your test suite easier to evolve. 🧠 Under the Hood WebApplicationFactory runs your app entirely in memory, while giving you an HttpClient bound to the test server. 🎯 The Result The Test Application pattern: - Real ASP.NET Core pipeline (middleware, DI, routing). - No ports, no containers, no infrastructure. - Clean code, configurable for each test, reusable across test cases. This pattern brings integration-test confidence with near-unit-test speed. A pattern I leveraged in my latest book. 💬 Would you swap containers for in-memory test apps in your setup? 💬 Are you already using WebApplicationFactory? 💬 What are your success/failure stories? This post continues my series on HttpClient & integration testing. It expands the original proxy testing article with bite-sized tips and new topics. (Link in comments 👇) #dotnet #testing #aspnetcore

90

10 Kommentare

.NET development is sometimes underrated, even in 2025 😞 Many think .NET is just: - Writing C# classes - Drag-drop in Visual Studio - EF Core scaffolding - Click “Publish” and you’re done But that’s just the tip of the iceberg. The reality? Professional .NET development is way more than building CRUD endpoints. A strong .NET Developer can: - Design clean architectures and follow SOLID principles - Model business domains (DDD) instead of dumping everything into one folder - Build Scalable Systems and Services - Optimize EF Core queries and transactions for real-world performance - Implement caching, distributed systems, and make APIs scalable - Secure applications using AuthN/AuthZ, Identity, OAuth - Build automated tests and ensure proper coverage - Review code, enforce branching strategies, and improve PR quality - Optimize hosting costs and design cloud-ready systems - And literally, so much more! .NET isn’t just a framework – it’s a discipline. Share this with someone who would want to read this.

2.750

73 Kommentare