staticwebapps

After my two previous posts Azure Static Web Apps: a first look and Azure Static Web Apps: quirks & gotchas, let’s have an updated look at ASWA in this post. Support for new languages 👩🏻‍💻 Announced at Microsoft Ignite this year, Blazor and C# APIs now supported in Azure Static Web Apps. This enables .NET developers to build and deploy full stack .NET applications with Static Web Apps. Blazor support Since ASWA is a static hosting option, which means we don’t have a server component*, the Blazor support for ASWA means support for Blazor WebAssembly.

After playing around with Azure Static Web Apps (ASWA) for some time I found some quirks and gotchas. Of course Static Web Apps are still in preview. Most of these are probably because of that fact. Despite that, it might still be interesting to know about them. That way if you run into any of them, you’ll at least know it’s not you … 😉 🏭 Creating an Azure Static Web App It all starts when you want to create an ASWA: searching for it in the list of resources in the Azure portal doesn’t show it.

Although the two have a lot in common, even including parts of the name, there are a few very clear differences between Static website hosting in Azure Storage and Static Web Apps. We’ll have a look at what those differences are and take a first look at the most recent of the two: Static Web Apps. Static website hosting in Azure Storage Static website hosting is a feature you can enable free of charge on a storage account.