Coding With David

Let’s face it: JavaScript and C# are like two exes that you just can’t quit. You need them both, but constantly bouncing between the two can leave you feeling a little...discombobulated. Enter Blazor , your ticket to full-stack development bliss—all in C# and .NET. No more switching personalities between the browser (JavaScript) and the server (C#). With Blazor, it’s all C#, all the time. So, why should you get excited? Let me count the ways. 1. C# for Full-Stack Development: The Dream Team Imagine being able to use your favorite language (yes, C#) to develop both the client and server side of your web app. No more learning JavaScript just to make a button do something fancy. Blazor lets you stay in your C# comfort zone , allowing you to share code between the client and server, reuse business logic, and bask in the glory of DRY (Don’t Repeat Yourself) principles. Who needs to switch languages mid-project when you can have a unified codebase? This means fewer mental context switches an

I heard about the HTTP files in Visual Studio when it first came out.  I researched the new feature of using Visual Studio to test your APIs. I thought it was cool, but I have been a long-time fan and user of Postman.  It is easy to use, has collections, can create tests, and most importantly is free. Over the last couple of years, Postman has made changes that require more configuration and overhead, but it is still a great tool.  Fast forward to my latest project where I needed to create a couple of simple APIs.  A basic Customer Crud and Order Crud. I went to fire up Postman, stopped, and thought this was a good option to try the Visual Studio solution for testing APIs. When you create .NET 8 web APIs, you get swagger for free.  Swagger is a nice tool but is more for documenting the APIs versus validating them.   What is a .http File solution in Visual Studio?  A .http file is a plain text file that you can create in Visual Studio to write and test HTTP requests. HTTP requests are t

  The feature of spell-checking in web browsers started gaining support around 2007. Specifically, Firefox 2, released in October 2006, was among the first mainstream browsers to include a built-in spell checker for text input fields. Other browsers, such as Google Chrome and Opera, followed suit in the subsequent years, incorporating similar features as they evolved. Since then, the support for spell-checking has become a standard feature across modern browsers, enhancing user experience by helping to identify and correct spelling errors in text inputs. Having spell check in the browser is a godsend for someone like myself, who can not spell. Spell check is a feature that identifies and highlights potential spelling errors in text. It is commonly used in word processors, email clients, and web browsers to assist users in correcting typos and ensuring proper spelling. In HTML , spell check can be enabled or disabled for text input fields, such as <input> or <textarea> , u

  In Visual Studio, there is a feature under Add – New – Item called "Add Scaffolding Item". After viewing a couple of  YouTube videos on how to use it, it got me thinking, is this a realistic feature, or is it just a nice demoable feature?   It does demo nicely. I decided to try it and see for myself how much value this feature can add for me when creating new applications that need CRUD actions. The Test Application To validate the scaffolding, I will be building a basic defect-tracking application using the scaffolding feature.   We will have only three issue types and will be using Entity Framework with an SQLite database.  I will be focusing on the scaffolding, not the features of the application. Granted it will be a scaled-down system, but there is CRUD used.  These are the issue types I will be creating:                1.       Bug – issue report from the internal team         2.       Defect – Like a bug but it was reported from a customer.        3.       User S