There are a few scenarios, especially when using partitioning/windowing T-SQL functions, that EF falls down a bit. It also is not entirely straight forward to perform somewhat complex joins and aggregation.
Complex EF joins and aggregation
posted on August 30, 2016 by long2know in Database, Entity Framework, LINQ
.NET Core Middleware Request Processing
posted on August 14, 2016 by long2know in ASP.NET, Core
Using the .NET Core Middleware for request processing is, imho, not very well documented. There are a couple of things that are not obvious: retrieving query parameters and binding a request body to an object. To top things off, accessing the request Body has a few issues. Here’s how to deal with these scenarios.
Creating a Distributed Computing Engine with the Actor Model and .NET Core
posted on August 13, 2016 by long2know in ASP.NET, Core
Over the past year and a few months, we, my coworkers and I that is, have been using an Actor Model framework to implement a sort-of state-engine-based distributing computing engine. Using a generalized framework for this seemed to introduce many complexities that, in my mind, could potentially be simplified. My weekend project is centered around exploring what can be done out-of-the-box with .NET Core.
Using EF6 with .NET Core
posted on August 10, 2016 by long2know in ASP.NET, Core, Entity Framework, MVC
EntityFramework 7 is the defacto ORM used with .NET Core to provide cross-platform compatible data access. EF7 is missing many features that are present in EF6, though. My initial apprehension was that this would create a scenario where one could not use .NET Core if their projects relied on EF6 features. Fortunately, it’s pretty easy to get EF6 working with .NET Core. The sacrifice is a loss of cross-platform hosting ability.
Handling ASP.NET MVC HttpAntiForgeryExceptions
posted on August 5, 2016 by long2know in ASP.NET, MVC
ASP.NET’s built in CSRF (Cross-site request forgery) is pretty straight forward. You add a token to your views via an HTML Helper, and then decorate your controller actions with a specific attribute to validate the token on POST. There are many times, seemingly randomly, where users have invalid tokens on their requests. MVC throws a 500 error with an HttpAntiForgeryException. For legitimate users, this is not an optimal experience.