.NET Core allows us to log just about everything very easily, but when something goes wrong with SQL queries, how exactly do you figure out where it’s coming from…?
This is where EF Core Query Tags comes into play, along with a couple of logging strategies, you’ll never be confused by the intent and location of your queries again!
About the speakers
Jernej "JK" Kavka
Jernej Kavka (JK) is an SSW Solution Architect, Microsoft AI MVP and organizer of the Brisbane AI user group. JK is a full-stack .NET developer, but his passion lies in Azure Cognitive Services, AI and machine learning. He is the main architect behind SSW's virtual receptionist - SSW SophieBot and SSW SophieHub: https://sswsophie.com
JK loves working on Blazor, Angular, .NET Core, and Cognitive Services. His most recent projects have featured Docker, AKS (Azure Kubernetes Services) and Machine Learning development. He loves containers and Kubernetes and enjoys showing others the immense possibilities that Container technology has to offer.
In addition to being an expert in ASP, .NET Core, Angular, and Azure DevOps, Jernej is also proficient on Windows platform development from legacy applications (using C#, WinForms, WPF, …) changing them into modern applications (using Windows Store, Windows Universal applications, and Xamarin). Lately, he's sharpening his skills with Cognitive Services as well as Machine Learning.
Related videos
