Coding With David

I have been spending some time working with Azure static websites and it got me thinking I should do a post about them.  The more I have been working with the Azure static websites, the more I like them. So I decided to dust off an old post, Static Bootstrap website converted to Blazor .  In this old post, I took a common Bootstrap-themed static website and "Blazorized" it. In the original project, I created components, removed as much of the javascript as I could, and used Blazor.  This was done back in Nov of 2019 as a server-side application.  This was right around the time Blazor server-side went GA and the Web Assembly was still at least 6 months left to go in development. For this post, I will be creating a Blazor Web Assembly version of the project that is built for Azure Static Websites and that actually works.  I hope to document as many of the changes as I can.   Once I fired up the old project, the project did not even compile anymore. ...

  I have several projects I have been looking at doing and I have been struggling with whether to use Azure functions or to build APIs and host them as an Azure app service. In this post, I am going to try to figure out what is the best solution based on functionality, reuse, cost, maintenance, and ROI. This post will not cover the in-depth technical difference between functions and web API.  The end result is for me to understand which one will work under a different use case. Advantages of Functions a. Code in the Browser     Not only am I not interested in this one, I think it is a disadvantage.  If you or your team are un-disciplined about your changes, a bad thing can happen. b. Additional languages supported     Not interested in this one either.  There is a side effect, what if a team member coded a function in Python and left the team, that supports it. c. Point and click integration with other Azure services like Blob Storage and Comos ...