Author’s Archive: long2know

Home / long2know
241 Posts

Continuing my series on porting to .NET Core, I have mostly converted a production .NET 4.5.x applcation to .NET Core 2.2.  As I mentioned, there are lots of conversion points that are worth mentioning for anyone else endeavoring to modernize a .NET application.

More Link

Continuing my (old) series on porting to .NET Core, I am sharing some of my experiences of moving a production, legacy .NET 4.5.x application to .NET Core 2.2.  This was a interesting endeavor since the application itself had some really deep hooks into the older WebAPI/MVC pipeline.

Ripping out those hooks is like opening the proverbial can of worms ..

More Link

Over the past few weeks, I’ve been working on making a legacy web application more accessible.  Key factors in accessibility are being keyboard and narrator friendly.  These factors are governed by various “A11yMAS” guidelines.  For this post, I’ll focus on a particular AngularJS datatimepicker (calendar) directive, which is used in the legacy web application, that lacked keyboard accessibility completely. 

More Link

A few weeks ago, I picked up a treadmill. It’s kind of nice having a treadmill during the winter months so that one does not have to run in the dark while the days are short.

I immediately discovered that the typical apps that I use on WearOS are painfully inadequate for recording indoor activities, though.

More Link

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.

More Link

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.

More Link