I have an Blazor Application which I build and want to deploy via Azure DevOps. So far that leads to a 500.30 startup error after the deployment when deployed via Azure but it works when I deploy directly out of Visual Studio via Web Deploy.
This is the yaml of my deployment task:
steps:
- task: AzureRmWebAppDeployment@4
displayName: 'Deploy Azure App Service'
inputs:
azureSubscription: '$(Parameters.ConnectedServiceName)'
appType: '$(Parameters.WebAppKind)'
WebAppName: '$(Parameters.WebAppName)'
packageForLinux: '$(System.DefaultWorkingDirectory)/**/*Server.zip'
JSONFiles: '**/appsettings.json'
I do have another asp.net core WebApp (just one with razor pages) in the same solution which was built and published with the same pipeline before. When I publish that zip via the same pipeline it works as expected.
I checked via FTP to see what is the difference and noticed that I can't see the files from the deployment via Azure. But when published via Visual Studio they are in the wwwroot. Do I have to configure something specially for Blazor?
EDIT: I did find out, that the issue is in my startup.cs. The reason I don't see the files has probably to do with the permission system of the folder. I also did find out that I can get a dump with the logfiles and the eventlog where more information are via Kudu:
Activity ID
from the azure devops pipeline log? – Merlin Liang - MSFTAzure File Copy
task. According to your issue, you mentioned that there's no files listed in its relevant path. I assume it should caused by the task used. Due to this detailed blog: chrissainty.com/deploying-blazor-apps-using-azure-pipelines – Merlin Liang - MSFT