Deployment of a Blazor WASM app from DevOps piepline results in path site/wwwroot/wwwroot/

Gerald Fischer 1 Reputation point
2021-01-08T15:48:22.8+00:00

Im building and deploying a .Net 5 Blazor WASM app from Azure Devops with the following pipeline to an Azure Web App, but the deployment adds an additional wwwroot directory inside the wwwroot directory, because the zip files get's extracted to the wwwroot directory instead of the site directory. The web.config resides in the top wwwroot directory, so simply changing the virtual path '/' to 'site/wwwroot/wwwroot' isn't an option. The result is that static files within e.g. wwwroot/css are not found.

I don't want to do any manual changes to the generated files and I'm wondering how that could be fixed, either by a different deployment style in DevOps, or by some setting I'm not aware of. Any help much appreciated.

  • job: Release
    displayName: Release to Azure pool:
    vmImage: 'ubuntu-latest' steps:
    • task: DotNetCoreCLI@2
      displayName: Publish the project
      inputs:
      command: 'publish'
      publishWebProjects: true
    • task: AzureRmWebAppDeployment@4
      displayName: Deploy the project
      inputs:
      ConnectionType: 'AzureRM'
      azureSubscription: ...
      appType: 'webApp'
      WebAppName: 'LikCompetition'
      packageForLinux: '$(System.DefaultWorkingDirectory)/**/*.zip'
Blazor
Blazor
A free and open-source web framework that enables developers to create web apps using C# and HTML being developed by Microsoft.
1,385 questions
{count} votes