The Cool Dev @devuatprod

@KarenPayneMVP With inline linq queries you can avoid weird joins that lambdas introduce. Where it matters for performance I go for inline linq and vice versa.

@_trish_xD .net core

@SumitM_X The question makes very little sense to be honest

@mjovanovictech Yes for more performant and precise database queries

@JLarky Yep i was part of that experiment as well

@timecaptales iPod

@ZdenekHrib skvely

Explore it here: github.com/The-Pocket/Poc…

Follow me for .NET Data news, tools & links - Azure SQL, EF Core, SqlClient, DacFX and more.. - and help me get closer to 10K followers. Feel free to RT 🙏

Modular on paper. Entangled in practice. Sound familiar? Your bounded contexts are probably overdue for a split. How bounded contexts rot in modular monoliths: - Every new feature ends up in the “core” module - Cross-cutting concerns sneak in (emails, logging, validation) - You can’t tell what owns what - Features are coupled, but don’t look like it Code organization is not architecture. Boundaries enforced at compile time? That’s architecture. And here's how to implement this: milanjovanovic.tech/blog/refactori…

𝗜 𝗵𝗮𝘃𝗲 𝗯𝗲𝗲𝗻 𝘄𝗮𝗶𝘁𝗶𝗻𝗴 𝗳𝗼𝗿 𝘆𝗲𝗮𝗿𝘀 𝗳𝗼𝗿 𝘁𝗵𝗶𝘀 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 Finally, it's coming in EF Core 10 preview 👇 It's 𝗟𝗲𝗳𝘁𝗝𝗼𝗶𝗻 and 𝗥𝗶𝗴𝗵𝘁𝗝𝗼𝗶𝗻 methods. Before .NET 10, I chained SelectMany, GroupJoin, and DefaultIfEmpty to fake a left join. Those long chains led to performance issues and risked client-side execution in production: when the join happened in memory, rather than a database. Before, when you made an 𝗜𝗻𝗰𝗹𝘂𝗱𝗲 - EF Core used SQL 𝗜𝗡𝗡𝗘𝗥 𝗝𝗢𝗜𝗡 behind the scenes. Now, you have more options on the JOIN type, you can use: ↳ 𝗟𝗲𝗳𝘁𝗝𝗼𝗶𝗻 - LEFT JOIN ↳ 𝗥𝗶𝗴𝗵𝘁𝗝𝗼𝗶𝗻 - RIGHT JOIN ↳ 𝗜𝗻𝗰𝗹𝘂𝗱𝗲 - INNER JOIN 📌 𝗟𝗘𝗙𝗧 𝗝𝗢𝗜𝗡 method returns all rows from the left table and the matched rows from the right table. If no match is found, NULL values are returned for columns from the right table. 📌 𝗥𝗜𝗚𝗛𝗧 𝗝𝗢𝗜𝗡 method returns all rows from the right table and the matched rows from the left table. If no match is found, NULL values are returned for columns from the left table. 📌 𝗜𝗡𝗡𝗘𝗥 𝗝𝗢𝗜𝗡 returns only the rows that match values in both tables. 👉 EF Core now translates both operators straight into SQL, giving you more control over the JOIN type in SQL. What do you think about these new methods? Do you see use cases for them? Leave a comment down below 👇 𝗜 𝗵𝗮𝘃𝗲 𝗯𝗲𝗲𝗻 𝘄𝗮𝗶𝘁𝗶𝗻𝗴 𝗳𝗼𝗿 𝘆𝗲𝗮𝗿𝘀 𝗳𝗼𝗿 𝘁𝗵𝗶𝘀 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 Finally, it's coming in EF Core 10 preview 👇 It's 𝗟𝗲𝗳𝘁𝗝𝗼𝗶𝗻 and 𝗥𝗶𝗴𝗵𝘁𝗝𝗼𝗶𝗻 methods. Before .NET 10, I chained SelectMany, GroupJoin, and DefaultIfEmpty to fake a left join. Those long chains led to performance issues and risked client-side execution in production: when the join happened in memory, rather than a database. Before, when you made an 𝗜𝗻𝗰𝗹𝘂𝗱𝗲 - EF Core used SQL 𝗜𝗡𝗡𝗘𝗥 𝗝𝗢𝗜𝗡 behind the scenes. Now, you have more options on the JOIN type, you can use: ↳ 𝗟𝗲𝗳𝘁𝗝𝗼𝗶𝗻 - LEFT JOIN ↳ 𝗥𝗶𝗴𝗵𝘁𝗝𝗼𝗶𝗻 - RIGHT JOIN ↳ 𝗜𝗻𝗰𝗹𝘂𝗱𝗲 - INNER JOIN 📌 𝗟𝗘𝗙𝗧 𝗝𝗢𝗜𝗡 method returns all rows from the left table and the matched rows from the right table. If no match is found, NULL values are returned for columns from the right table. 📌 𝗥𝗜𝗚𝗛𝗧 𝗝𝗢𝗜𝗡 method returns all rows from the right table and the matched rows from the left table. If no match is found, NULL values are returned for columns from the left table. 📌 𝗜𝗡𝗡𝗘𝗥 𝗝𝗢𝗜𝗡 returns only the rows that match values in both tables. 👉 EF Core now translates both operators straight into SQL, giving you more control over the JOIN type in SQL. What do you think about these new methods? Do you see use cases for them? Leave a comment down below 👇 ♻️ Follow me @AntonMartyniuk and repost this to help others 📌 Save this post for future reference!

keyboard_arrow_left Previous keyboard_arrow_right Next

Boolean parameters are a Code Smell. Here's an example: user.SetStatus(true); // ← What does 'true' mean here? It might be "active", "enabled", or "verified". But it isn’t obvious — and that’s the problem. A better approach? Make the method express intent with an explicit method. No booleans. No guessing. No comments needed. --- Do you want to simplify your development process? Grab my free Clean Architecture template here: milanjovanovic.tech/templates/clea…

@DevLeaderCa I really want to try that out. I might introduce it on an internal tool just to give it a shot. I haven't checked but is it easy to introduce it side by side next to MVC?

C# 14 in the preview allows the null conditional member access operator on the left-hand side of an assignment. Previously, you had to check if the customer was null before assigning the order. In C# 14, the GetCurrentOrder method is not called if the customer is null.

Seven years after we first launched, we’re opening a whole new chapter of Uno Platform evolution, redefining dev productivity —ANNOUNCING: 👉 Uno Platform Studio General Availability 🚀 👉 Uno Platform 6.0 – reengineered, lean, fast, and easy to use (3x faster startup, 45x faster execution) 🧵Let’s break down this EPIC release ⬇️

.NET devs coming back to ASP .NET MVC after trying Blazor, Razor Pages and Minimal APIs

He has a point though right? 🤣👀 #dotnet AI dangerous in the wrong developer hands?

@okyrylchuk Option 4 - somehow got used to pattern matching

@Dave_DotNet I feel that is the most crucial part of any application.

Entity Framework is not slow 🤣 #dotnet