Sponsorship is available! If you’d like to sponsor CodeOpinion.com and have your product or service advertised exclusively (no AdSense) on every post, contact me.
Here are the things that caught my eye recently in .NET. I’d love to hear what you found most interesting this week. Let me know in the comments or on Twitter.
System.Text.Jsonfocuses primarily on performance, security, and standards compliance. It has some key differences in default behavior and doesn’t aim to have feature parity with
Newtonsoft.Json. For some scenarios,
System.Text.Jsonhas no built-in functionality, but there are recommended workarounds. For other scenarios, workarounds are impractical. If your application depends on a missing feature, consider filing an issue to find out if support for your scenario can be added.
Nothing can be more frustrating than going into a situation “thinking” you know how a framework works, only to spend the next several hours pulling your hair out and stewing in a pot of unhealthy feelings. I like to consider myself an ASP.NET routing expert with my experience dating back to MVC 1.0. Recently, I’ve started using ASP.NET Core Razor Pages mixed in with MVC and API approaches. I find the combination of all this technology to be a winning one, but it can also add complexity when building views. In this post, I’ll show you a simple one page Razor Page that can help diagnose route resolution issues quickly. Quickly see what your ASP.NET Core application sees and what it requires to resolve routes.
EF Core 5.0 introduces the
ToQueryStringextension method which will return the SQL generated by EF Core when executing a LINQ query.
Instead, EF Core 5.0 introduces
CreateDbCommandwhich creates and configures a
DbCommandjust as EF does to execute the query.