This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 99%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJC%3C/text%3E%3C/svg%3E)
We have created a Linux-based Azure Web App Service running dotNet Core 6.0 in our Azure tenant, and want to use Azure DevOps to create a pipeline for deploying code to the dev slot of the app service.
I have been reading up lots of official Microsoft documentation on how to do this, but I am still stuck. We are able to build the pipeline, and deploy a release. The result is successful, but when we actually browse to the web app, the page says " :( Application Error If you are the application administrator, you can access the diagnostic resources."
I am not a developer, but I have been tasked with getting this pipeline setup. This is the most complex pipeline tool I have seen. Can anyone assist with this? I can provide whatever logs or details you need
Thank you!
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
first publish the project (via dotnet publish or vs) to a filesystem, so you know what the deployed file structure should be. then compare this to the deployed file structure.
also check the logs on the server. often its deployed properly, but a configuration value crashes the app at startup.
Hi Bruce,
Thank you for your reply and it has brought me to a useful conclusion, although it is a mystery still. I published the project and viewed the files, and went to compare it to what the pipeline published. However I noticed the pipeline does not have any published artifacts... Why is this?
UPDATE: Okay I was able to get the pipeline to generate an artifact by adding this to my YAML file, however now there is nothing in the artifact...
# this code takes all the files in $(Build.ArtifactStagingDirectory) and uploads them as an artifact of your build.
- task: PublishPipelineArtifact@1
inputs:
targetPath: '$(Build.ArtifactStagingDirectory)'
artifactName: 'bma_webinar_site'