Azure DevOps Continuous Integration with asp.net web forms website project instead of web application

1
votes
##[debug]check path : d:\a\_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.158.3\task.json
##[debug]adding resource file: d:\a\_tasks\PublishBuildArtifacts_2ff763a7-ce83-4e1f-bc89-0ae63477cebe\1.158.3\task.json
##[debug]system.culture=en-US
##[debug]PathtoPublish=d:\a\1\a
##[debug]check path : d:\a\1\a
##[debug]ArtifactName=drop
##[debug]ArtifactType=Container
##[debug]system.hostType=build
##[warning]Directory 'd:\a\1\a' is empty. Nothing will be added to build artifact 'drop'.

Want to create artifact for Asp.net web forms website, but no files are being added to artifacts. Hence, artifact is not generating. Want to deploy it on Azure Web App service.

1
asp.netazure-devops

1 Answers

0
votes

According to your description, you are building a legacy "WebSite" (Asp.net Web Forms Stie) project type which is deprecated now while the "Asp.Net" template in the Azure DevOps definition is used for "Web App" project type.

Check the difference here: ASP.NET Web Site or ASP.NET Web Application? And for website project, there is no need to build them since they are automatically compiled on web server, you just need to deploy the source file to server directly. I also recommend you to use "Web App" to create your project since "Web Site" is deprecated.

Well, back to your question. For the Asp.net web forms website you need to update the pipeline (build definition) by adding a "Copy Files" task to copy the WebSite from its folder (source folder) to $(build.artifactstagingdirectory) to publish the artifacts.