tag:help.appveyor.com,2012-11-13:/discussions/problems/17750-package-aspnet-core-projects-does-not-create-artifactsAppVeyor: Discussion 2019-03-08T02:27:00Ztag:help.appveyor.com,2012-11-13:Comment/463870162018-10-30T01:48:08Z2018-10-30T01:48:10ZPackage ASP.NET Core projects does not create artifacts<div><p>Hi, I've read the forums about artifacts not being created for ASP.Net Core projects, and they mention using "dotnet publish" in a post-build command. I've actually got this working and my artifacts are generating. However I'm having problems with locked files on the Azure server and anyway, I just want to go back to basics because I'm afraid I'm overcomplicating things.</p>
<p>My questions arises because none of the forum articles mention what appears to be a new flag in the UI:</p>
<p>Settings -> Build -> Automatic packaging -> Package ASP.Net Core projects.</p>
<p>I've included a screenshot. You can see I've included the Web Applications as well - this is because I will eventually have regular .Net projects in the solution too. I don't believe it should impact my issue though.</p>
<p>So, my question is - why does selecting this new option not result in artifacts being created after my build?</p>
<p>I'm using ASP.Net Core 2.1</p>
<p>Thanks very much,</p></div>Ben Lieberttag:help.appveyor.com,2012-11-13:Comment/463870162018-10-30T22:33:16Z2018-10-30T22:33:16ZPackage ASP.NET Core projects does not create artifacts<div><p>Hi Ben,</p>
<p>Apparently we regressed this functionality. Filed <a href="https://github.com/appveyor/ci/issues/2719">this issue</a>. Will deploy fix asap, by the end of the week or so (cannot give exact date right now).</p>
<p>However the way you package artifacts should not affect problems with locked files on the Azure server. Let us try to understand this problem. I assume you are deploying to Azure App Service. How do you deploy? With <a href="https://www.appveyor.com/docs/deployment/web-deploy/">Web Deploy</a> or <a href="https://www.appveyor.com/docs/deployment/azure-app-service-zip-push-deploy/">Zip push</a>? Your build configuration in YAML format will not hurt too.</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/463870162018-10-30T22:41:40Z2018-10-30T22:41:40ZPackage ASP.NET Core projects does not create artifacts<div><p>Thanks Ilya, please keep me posted as to when the fix is in place.</p>
<p>I started with YAML, but the simplicity of your UI is more attractive :)</p>
<p>Yes, the locked files will be unrelated - definitely an Azure thing I'm<br>
sure. I'm using Web Deploy. It's all just new so I'll wait until I've got<br>
AV going with your update and then I'll work on the locked files if they<br>
still persist.</p>
<p>Appreciate the quick feedback - Ben</p></div>Ben Lieberttag:help.appveyor.com,2012-11-13:Comment/463870162018-10-30T23:15:17Z2018-10-30T23:15:17ZPackage ASP.NET Core projects does not create artifacts<div><p>Welcome :) You can send configuration in YAML format, by exporting UI config with <code>Export YAML</code> button. But this maybe not needed now, because I strongly recommend using Zip Push deploy, It was designed to address most of Web Deploy issues with Azure App Service. If you do not have strict dependency on it like <a href="https://www.appveyor.com/docs/deployment/web-deploy/#web-deploy-parametrization">particularization</a>, nothing should stop you from switching to Zip Push.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/463870162019-03-08T02:26:45Z2019-03-08T02:26:45ZPackage ASP.NET Core projects does not create artifacts<div><p><a href="https://github.com/appveyor/ci/issues/2719">https://github.com/appveyor/ci/issues/2719</a> is fixed, should work now.</p></div>Ilya Finkelshteyn