In this part I'll extend the application with some basic data management capabilities. This includes listing all your created data item types, your drawing uploads, showing detailed information and providing you options to delete one or more items from the Azure Maps Creator environment.

Last month we had the annual Microsoft Build conference and, as always, a lot of exciting new things were announced. Instead of giving you a rundown of all the shiny new bits (which can be found in a lot of other places), I decided on building a proof of concept in which a couple of these new parts will be used together.

Since .NET 5 you can use CSS isolation to create component scoped CSS files. Did you know something similar was introduced for JavaScript as well? Plenty of examples can be found online to get this working in your Blazor app. But what if the basis for your JavaScript is actually TypeScript? Then good samples are a lot harder to find. In fact I did not find any sample where multiple modules where being used. This post outlines the steps I took to get exactly this up and running.

The standard design you get out of the box when creating a Blazor application is based on Bootstrap. It doesn't matter whether you go for a server side or a web assembly implementation. But what do you need to do if you would like to use a different design? Say, for example, dress up your app in the Microsoft Office 365 look. This post shows you your options to achieve exactly that.