Trouble Loading in Deployed Environment (Azure App Service)

[Mike-E-angelo]

Greetings,

I have recently deployed my Blazor Server-side application .NET 9 to an Azure App Service. With local development everything loads correctly. However, in the Azure App Service none of the Microsoft.FluentUI.AspNetCore.Components css or js loads.

I have to add the following script tag for this library to load as expected in an App Service environment:

<script src="_content/Microsoft.FluentUI.AspNetCore.Components/Microsoft.FluentUI.AspNetCore.Components.lib.module.js" type="module"></script>

Based on the documentation that I have seen, this shouldn't be necessary, so I am writing here to see what is occurring in App Service that isn't occurring locally during development.

Thank you for any assistance you can provide in tracking down this issue.

[vnbaaij]

I'm guessing it is something with a path that is different on App Service. Are you seeing any errors in the browser console when running the app without the manually added script tag?

[Mike-E-angelo]

Thank you for the suggestion @vnbaaij it is appreciated. Checking the console was my first guess as well, but no errors/warnings are displayed. Very curious and perplexing. 🤔

[Mike-E-angelo]

Another potential clue @vnbaaij: FluentTabs with DeferredLoading="true" works perfectly well in local development:

But in deployment on App Service, they do not load as expected (no errors/messages/warnings are emitted):

[vnbaaij]

Interesting.

Unfortunately, we do not have time to go on a wild goose hunt to track this down. We really need to have an (easy) way to reproduce this. Is that something you can help us with?

[Mike-E-angelo]

I totally understand @vnbaaij, and my primary intention here is to see if you are aware of anything reported thus far that might indicate what is happening. As for an easy way to reproduce, how would I do this? It works fine and is expected in local development, but not when I deploy to App Service. 🤔 The primary concern here is that any obvious diagnostics should be output in such a case. If there was some way to get additional diagnostics to track this down, it would be valuable.

[vnbaaij]

No, we have no clue as to why this is happening.

As for an easy way to reproduce, how would I do this? It works fine and is expected in local development, but not when I deploy to App Service. 🤔

Yeah, that is exactly my problem as well. To try to reproduce, I need to:

1. Build a site,
2. Deploy to Azure App Service
3. Start to chase down what is happening. No clue where to start so repeat 1 and 2 many times, will take a lot of time.

The primary concern here is that any obvious diagnostics should be output in such a case. If there was some way to get additional diagnostics to track this down, it would be valuable.

Maybe you can try to deploy a debug build of your app to the App Service (in a test environment)?