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.
Angular Datepicker – Exploring Bootstrap (Part 3)
posted on December 8, 2017 by long2know in angular, plunker
Angular Formatting Data
posted on November 28, 2017 by long2know in angular, plunker
A while back, I blogged about an Angular Table component that I wrote. Since that time, this component has expanded a fair bit as my application needs grow. Once such feature that I needed recently was the ability to format data dynamically.
Angular Dynamic Routes and Application Initialization
posted on November 15, 2017 by long2know in angular
As I’ve been using my latest Angular demo which is Visual Studio based increasingly in production applications, I’m finding more and more things that I have to port from the older AngularJS templates that I had put together. Today, I needed to understand and develop a means to dynamically handle routing and application configuration (initialization).
Angular Toast (Growl) Notifications
posted on November 3, 2017 by long2know in angular
In my older AngularJS applications, I used a jQuery plug-in plus AngularJS singleton “notification” service whenever I wanted to display toast/growl notifications. With the newer Angular framework, I started going down this path, but did also play around with an Angular module that provides this functionality.
Angular 5.0 released
posted on November 2, 2017 by long2know in angular
Yesterday, Angular 5.0 was released. The Angular team provides a handy upgrade guide to help with upgrading from any previous version of Angular. Upgrading from 4.x was pretty straight-forward.
.NET Core Generic Repository Dependency Injection
posted on October 26, 2017 by long2know in Core
This morning I was updating some Data Models in a project, and noticed, based on my project scheme, that I would have to add a derived BaseRepository class. This is a side-effect of the way I’ve used Ninject for a long time and every IRepository<T> is specified to be a BaseRepository<T>. That pattern is a little annoying, and in some ways, is counter-intuitive when dealing with DI and generics.
.NET Core Factory Pattern for Multiple Mappers (AutoMapper)
posted on October 17, 2017 by long2know in ASP.NET, Core
A friend of mine asked me yesterday how one would go about having an AutoMapper configuration such that you have multiple mappings for the same object pairs. This is an interesting situation for which I didn’t have an immediate answer. But, after playing around with AutoMapper a bit, my choice was to utilize a factory to provide multiple IMapper instances.
Migrating Angular 4.x Plunks to a VS2017 .NET Core 2.0 Project
posted on October 11, 2017 by long2know in angular, ASP.NET, Core, JavaScript
I’ve written a fair bit of demos for Angular 2.x/4.x using Plunker. Plunker provides a pretty convenient way to demo Angular concepts, but the fact that the code is rendered in the browser doesn’t make it overly useful for building redistributable, or production, applications. Since many people have asked me how to take some of my demos from Plunker to a Visual Studio project, that’s what I decided to do.
Using Quartz to manage Concurrency
posted on October 3, 2017 by long2know in ASP.NET, Core, Quartz
A while back, I blogged about using Quartz for scheduling jobs. Recently, I needed to make an API that could trigger jobs, and I thought of Quartz. There is a need/desire in this use case to prevent concurrent execution of jobs when the API is accessed and triggers jobs, and I didn’t really want to stack/queue jobs either. Quartz has some nice mechanisms to achieve exactly what I wanted.
.NET XmlSerializer memory leak
posted on September 26, 2017 by long2know in ASP.NET
A memory leak can very difficult to isolate. I ran into an interesting one a few days ago. I have a service that makes calls to a SOAP service with a serialized SOAP body from POCO, and it digests/deserializes the Xml response into POCO. However, there was a memory leak that I could not locate.