Trying to get a Blazor WASM + API Web Application Running

Question

Hello Microsoft Azure Support,

I have been trying to get my azure web application working that uses a Blazor WASM frontend, an ASP.NET backend, and a shared library between the two of them for entities and models.

Whenever I try to get them running, I keep seeing the logs comeback with this warning: DotNet Runtime 10.0WARNING: Expected to find only one file with extension '.runtimeconfig.json' but found 2.

When trying to fix this warning, I keep getting recommended to go into the Configuration -> General Settings -> Startup Command. However, I am unable to find the start-up command option within the general settings.

Would you be able to show me where I can go to get over to the Startup Command settings so that I can place in the necessary command to use the .dll file?

Thank you very much for your help,
Andrew

Answer 1

Hello @Andrew Sabin

Thank you for reaching out Microsoft Q&A, startup command are customized commands. Providing the documentation below for better understanding.

https://learn.microsoft.com/en-us/azure/app-service/configure-language-python#customize-startup-command

Multi-project solutions or NuGet packages create duplicate .runtimeconfig.json files. This might be the reason for warning shown.

Try clean publish to mitigate this warning.

Answer 2

To address the warning about multiple .runtimeconfig.json files, you should ensure that your application is correctly configured to avoid such conflicts. Regarding the Startup Command settings in Azure, the option to set the startup command can typically be found in the Azure Portal under your web app's configuration settings. Here’s how you can navigate to it:

1. Log in to the Azure Portal.
2. Navigate to your Web App: Find your web application in the list of resources.
3. Configuration Settings: In the left sidebar, look for the Configuration option.
4. General Settings: Within the Configuration section, you should see General settings. Here, you can set various options for your web app.
5. Startup Command: If your web app supports it, you should see a field for Startup Command. If you don’t see this option, it might be due to the type of hosting plan or configuration you are using.

If you are unable to find the Startup Command option, ensure that your web app is set up correctly for the type of application you are deploying (e.g., Azure App Service vs. Static Web Apps). You may also want to check the documentation specific to the type of Azure service you are using for further guidance.

---

References:

• ASP.NET Core Blazor startup
• Host and deploy ASP.NET Core Blazor WebAssembly