Earlier today, I was struggling a bit to get a .NET Core application’s authentication mechanism to behave appropriately for both MVC (view) and API (ajax/json) requests. In .NET Core 2.x, handling this is not as straight-forward as it could be, but it’s doable. Effectively, we want a user requesting a view through a normal browser request to get an authentication challenge / login page, but we want API requests to receive a 401 response and end it there. Under normal circumstances, though, both types of requests would receive the login page.
Disabling Automatic Authentication Challenge in .NET Core 2.x
posted on June 14, 2018 by long2know in ASP.NET, Core
Upgrading from Angular 5 to 6
posted on May 9, 2018 by long2know in angular
In case you missed it, Anuglar 6 was released a few days ago. I decided to take one of my primary Angular 5 projects and upgrade it. Man, it was painful ..
Handling Custom Exceptions with .NET Core Middleware
posted on May 3, 2018 by long2know in Core
A while back, I blogged about integrating client/server validation. I wanted to take this same concept a bit further with custom exception handling and .NET Core Middleware to make a more reusable delivery mechanism.
Angular Custom Error Handler
posted on March 2, 2018 by long2know in angular
Angular has built-in mechanisms for dealing with unhandled exceptions. In an application, we only need to provide this handler when we want to customize the display and handling of errors.
.NET Core Open Generics with Factory Pattern
posted on February 28, 2018 by long2know in Core
A while back, I blogged about using open generics with .NET Core Dependency Injection. It really does work great for an out of the box experience. However, one drawback is that you can’t use a factory pattern like you can when injecting in a type-specific way.
.NET Core Console App Dependency Injection and User Secrets
posted on February 19, 2018 by long2know in ASP.NET, Core
The other day, I wanted to create a really simple console application using .NET Core 2.x. Out of the box, however, it appeared that there were a lot of compromises to a console application as compared to a Web/Kestrel hosted app. The main things that were missing were dependency injection and user secrets.
Entity Framework and the Magic of Nothing
posted on January 26, 2018 by long2know in Core, Entity Framework
Last night I was working on a project that had some many to many database relationships. On one side of the relationship, someone decided to use zero as the default “nothing selected” sort of key. This simply doesn’t work with Entity Framework, or probably most other .NET ORMs.
Angular Event Emitters with RxJS Subscriptions and Subjects
posted on January 26, 2018 by long2know in angular, plunker
While I was working through my post regarding generically formatting Angular data within a component, another generic implementation that I needed arose. I needed a way to, in a very generic fashion, raise events from a child component to its parent. Within the context of an Angular table, this could typically coincide with a click event that needs to take action, or apply some logic, to the child’s bound data. Event Emitters in Angular readily facilitate this type of functionality.
Angular User Session Timeout
posted on December 20, 2017 by long2know in Uncategorized
A long time ago, I blogged about a service that I used in AngularJS to let the user know that their session is about to expire and that they would be logged out if they didn’t take action. I needed to recreate this functionality in Angular for my latest swath of applications.
Angular Datepicker – Exploring Bootstrap (Part 3)
posted on December 8, 2017 by long2know in angular, plunker
Since I’m using a lot of Angular Bootsrap components in my Angular apps, now seemed like a good time to revisit the classic Datepicker. The Angular Bootstrap Datepicker is relatively easy to get up and going, but I did run into a few quirks.