C

Your integration tests all pass, but your live app throws a cryptic EF Core error about modifying a key that doesn't even exist. Let's dive into the fascinating reason why and how to fix it.

A couple days ago I needed to call a remote web api call in my AuthorizeAttribute sometimes but as mentioned in this (Is it possible to use async/await in MVC 4 AuthorizeAttribute?) StackOverflow question (and other forums) it isn't supported but is in the newer .net core. Unfortunately the project I needed this on was traditional MVC so I was left still finding a way .

I've recently started catching up with all the blogs that I've wanted to write and have had flagged to write for a long time. This one I have had flagged since 26 January 2016.