Azure的ASP.NET RC1部署失败 [英] Azure ASP.NET RC1 Deployment Failure

问题描述

我有一个通过GitHub的部署部署到Azure中的ASP.NET核心RC1应用程序（即我承诺源GitHub上，应用程序内置/湛蓝的部署）。

I have an ASP.NET Core RC1 application that is deployed to Azure via GitHub deployment (i.e., I commit source to GitHub and the application is built/deployed by Azure).

一切正常，直到某个时候在过去5天。我成功地部署我的应用程序3天前（〜2016年5月16日）。今天我做了更改，并试图再次部署，但部署失败。我试图再次部署（思考这个问题可能是暂时的），并遇到同样的问题。然后，我尝试重新部署previous已知的良好承诺，这再次失败（注： project.lock 在源代码控制）。然后我滚回去师傅已知好的previous推由此引发的另一个部署，同样的错误。

Everything worked fine up until sometime within the last 5 days. I successfully deployed my application 5 days ago (~2016-05-16). Today I made a change and tried to deploy again but the deploy failed. I attempted to deploy again (thinking the problem may be transient) and encountered the same problem. I then tried re-deploying the previous known good commit, which failed again (note: project.lock is in source control). I then rolled master back to the previous known good and pushed which triggered another deploy, same error.

这可能只是一个巧合，但与RC2，因为我previously尝试了部署发布显著重大更改。

It could be just a coincidence, but RC2 with significant breaking changes was released since I previously attempted a deploy.

在我的部署日志来看，第一个错误是：

Looking at my deployment log, the first error is:

Failed to resolve conflicts for DNX,Version=v4.5.1

Unable to satisfy conflicting requests for 'Microsoft.Extensions.Configuration':
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.ApplicationInsights.AspNet 1.0.0-rc1-update4),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.AspNet.Hosting 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Json 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final),
Microsoft.Extensions.Configuration (>= 1.0.0-rc1-final) (via package/Microsoft.Extensions.Configuration.Binder 1.0.0-rc1-final)"

我得到的是错误的整体转换（无法满足冲突的请求... ）各种传递性依赖。

由于这个项目的成功部署3天前与一个特定的提交/ project.lock ，我要承担的东西在Azure中还是的NuGet已经改变导致此。

Since this project successfully deployed 5 days ago with a particular commit/project.lock, I have to assume something has changed in Azure or NuGet to cause this.

我删除了本地的NuGet包缓存，并能在Visual Studio和VS code成功重建。

I deleted my local NuGet package cache and was able to successfully rebuild in Visual Studio and VSCode.

在故障排除步骤任何意见是值得欢迎的。

Any advice on troubleshooting steps is welcome.

推荐答案

这发生了，当RC2发布，这导致的一个问题与RC1部署。请使用以下解决方法（从<一个href=\"https://social.msdn.microsoft.com/Forums/en-US/9840ce88-6479-46b2-a312-7ac6a41366a4/rc1-web-site-cant-be-updated-anymore?forum=windowsazurewebsites$p$pview\"相对=nofollow>这里）：

This happened when RC2 was released, which caused an issue with the RC1 deployments. Please use the following workaround (from here):

• 复制.deployment和deploy.cmd从 https://github.com/davidebbo-test/AspNet5RC1


• 编辑<一个href=\"https://github.com/davidebbo-test/AspNet5RC1/blob/0e42059b5a9938ea9605542b88199f740baec55c/deploy.cmd#L96\"相对=nofollow>此行中的deploy.cmd指向您的project.json


• 此外，如果你的项目是不是 RC1-UPDATE1其他东西（例如，如果它在 beta8 ），你会需要这个文件来修复了所有的RC1引用（有两个）。


• 在您的存储库根提交这两个文件。

• Copy .deployment and deploy.cmd from https://github.com/davidebbo-test/AspNet5RC1
• Edit this line in deploy.cmd to point to your project.json
• Also if your project is on something other than rc1-update1 (e.g. if it's on beta8), you'll need to fix up all the rc1 references in that file (there are two).
• Commit both files at the root of your repository.

话虽这么说，你应该寻找到移动到RC2：）

That being said, you should be looking into moving to RC2 :)

这篇关于Azure的ASP.NET RC1部署失败的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！