
Obscure error during switching of Azure SWA Functions from in-process to isolated mode
A couple of years ago I crafted an internal-use utility for one of my clients that uses Azure Static Web Apps with Blazor and some Functions. That worked well, but the client asked to extend functionality, so I decided to refresh the code along the way. Back in the day, I wrote the utility using .NET 6 and in-process functions, since the out-of-process mode was not yet available. The current .NET 8 shifted focus to the out-of-process mode, which is much better and less tied to Azure SDK code. However, according to the Azure Functions docs, they still supports in-process mode, so I anticipated an easy migration. Well, I totally misjudged that! ...
