VSCode is a fantastic IDE for editing <insert your favourite language here> source code. Likewise Angular is a great framework for developing front-end web apps.
When developing applications, we developers usually spend most of our time in the debugger. However, out of the box there is a little bit of setup required to enable debugging of an Angular TypeScript application when using VSCode.
In this post I'll show you how to configure VSCode debugging for an Angular TypeScript application with the Google Chrome web browser.
If you work JSON documents, I'm sure you've probably had to create a class file from a JSON string. Doing this manually can be a real pain in the proverbial, especially if you are working with a large JSON document. It can also be very error-prone. Therefore it's best to automate this conversion.
In this post I'll show you how to automatically generate a class file from a JSON string using a little known feature built into Visual Studio.
While working on a Blazor WebAssembly solution that used Steve Sanderson's BlazorInputFile solution I came across an unusual issue where the “No File Chosen” text would not change and the selected filename did not appear even though a file had already been selected.
Let’s face it … security is HARD. Implementing authentication and authorization into applications has always been a challenge and a chore for developers. Building a secure application requires strong knowledge across a number of areas.
Thanks to the power of Microsoft Azure, it now doesn’t have to be like this anymore. Thanks to the power of Easy Auth it’s easier than ever to setup secure authentication for your web application with the click of a few buttons. Yep, I’m not kidding!
I’ve been working on a Google Chrome Browser Extension but had some trouble integrating it with Google Analytics. Google's own tutorial hadn’t yet been updated to use the new analytics library. In this post I'll explain how I did it.
In today’s rapidly evolving world of technology there has always been a clear distinction between mobile apps and websites. They each bring along their own set of pros and cons.
Although native mobile apps provide a first class user experience, they tend to have a higher barrier to entry; they require installation and are typically more difficult to develop/maintain. Websites on the other hand are platform agnostic and are typically easier to develop and maintain, however they provide a less engaging user experience.
In this article I'll touch on a new technology called Progressive Web Apps which aims to bring these disparate worlds together. It may very well be the future of the web!