Mark Johnson

Software EngineerLucky HusbandProud FatherHopeless NerdAmateur BuilderDisney FanaticNeglectful Blogger

ASP.NET Core Identity Without Entity Framework

Posted on: September 9, 2017/  Posted by:  /  No Comments
When ASP.NET Identity was introduced back in 2013 it represented a huge step forward in extensibility and flexibility over its predecessors. Out of the box, it used Entity Framework to make it super easy to go from “File -> New Project” to a fully functional web application with support for user registration and login. Of …
More

The Perfect Two Week Disney World Plan

Posted on: March 19, 2017/  Posted by:  /  No Comments
The Plan You should stay in a Disney resort if you can. There are 18 uniquely-themed resorts operated by Disney throughout the property, so you’ll have no trouble finding something that fits your personality and your budget. You’ll also want to get a 10-Day ticket to the theme parks, which provides the most bang for …
More

Exorcising Entity Framework from ASP.NET Identity

Posted on: January 11, 2014/  Posted by:  /  41 Comments

ASP.NET Identity is Microsoft’s fourth and by far its best iteration of an authentication/authorization system that’s built right into ASP.NET. It’s super flexible and extensible, yet easy to use and ready to go right out of the box. That ease of use is achieved in part thanks to a default backing store provider based on …

More

ASP.NET MVC Model Binding with Knockout

Posted on: June 29, 2013/  Posted by:  /  2 Comments

Knockout is a JavaScript-based MVVM framework. If you’re reading this article I’m going to assume that you already know what Knockout is all about and are interested in using it in your ASP.NET MVC application. However, if you’re new to Knockout, I highly recommend checking out the official website at¬†knockoutjs.com. Let’s take a typical example …

More

Flatten a C# Hierarchy

Posted on: January 27, 2012/  Posted by:  /  No Comments

I had a need this week to flatten a similar hierarchy of objects into a single list. I figured there must be a fancy Linq extension to do the job so I headed on over to MSDN only to discover that there isn’t. So I decided to write my own extension to flatten any similar object hierarchy.