After successfully publishing my first Blazor app, I started getting a bunch of 404 errors on my application insights dashboard.
What are these errors? Why? What does this mean?
Well, it turns out, Apple devices make those requests assuming your apple-device-optimized website will contain these files. These files are used by the device when the users bookmark your site to their home screen. If you don’t provide these files, your site icon will be an ugly screenshot of your site.
Ok, how do I fix it?
It’s a simple fix, just upload a single 180x180px PNG image to your website root and declare it in the head of your site.
Blazor is a new client-side UI framework from the ASP.NET team.
Ok, but what does this mean?
WebAssembly vs Server
Blazor comes in two flavors: WebAssembly and Server. With Blazor, you can either run your code directly in the browser using WebAssembly or on the server, communicating UI using SignalR.
When creating a new Blazor app with Visual Studio, it will ask you to set some initial configuration.
For this case, I selected WebAssembly and checked the “ASP.NET Core hosted” checkbox, this will configure the app to use an ASP.NET Core backend.
Note: Blazor also allows you to create a Progressive Web Application out of the box, but I’ll leave this for another time.
This setup will create the following solution structure:
The solution contains a client application, a server API, and a shared library; all you need to start coding… You’ll see that there are several example files, and if you go straight and run the project, you’ll find a simple weather application that will help you get familiar with the inner workings of Blazor.
Among the example files, you’ll find a shared model in the shared library, some controllers that return some mock data on the server project, and a few pages and components in the client application… Sounds familiar, right? Blazor components are building blocks for your application; a component in Blazor is an element of UI, such as a page, dialog, or data entry form.
I wanted to get some hands-on experience with Blazor, so I created a simple web application using the WebAssembly approach. It is a very straightforward application that lists and filters a song directory for a karaoke night.
The code is quite simple; client application makes a GET request to API, which reads a JSON file, deserializes it, and returns a list of songs. It is basically an alternate version of the sample application included with the template.
You can take a deeper look at the code in GitHub.
Blazor is an exciting platform for web developers and a compelling alternative to the current web application frameworks. There are issues and aspects where Blazor feels not mature enough, but there is an active community of developers working to make it better and strengthen its weak points. I believe we’re going to see a lot of Blazor in the next years; we just need to wait for more developers to start creating with Blazor.
I remember when we delivered software on floppy disks, it was quite different back then… In today’s market, we don’t deliver software as a product anymore; we deliver software as a service… We need to change how we do things, one step at a time.
Daniel Snaith, aka Caribou, has that mix of electronic beats that get me in the mood. A veteran producer, he has a particular interest in long DJ performances. I think this may be the reason why I find it so good to focus and start a coding session.