kudu: Git Deployment of ASP.NET Core fails with 'error MSB1009: Project file does not exist'

We have been deploying through Continuous Integration to Azure App Services for quite a bit, today, our builds are broken due to a change on the dotnet CLI.

Right now we see on Kudu that the current CLI version is 1.0.0-preview3-004056. If the App is an ASPNETCore app (xproj / project.json) it’s failing to find the project.

The App Service activity log shows:

Manually running dotnet build on Kudu console shows:

Repro repo available: https://github.com/ealsur/mvpstream

About this issue

Original URL
State: closed
Created 8 years ago
Comments: 40 (23 by maintainers)

Most upvoted comments

Can you try adding this global.json at the root of your project?

{
  "projects": [ "src", "test" ],
  "sdk": {
    "version": "1.0.0-preview2-1-003177"
  }
}

If you don’t have it, then it uses whatever is the latest Core sdk on the box, which changes over time (we now have the new Preview3, which is incompatible).

davidebbo on Nov 16, 2016

Linking to forum thread and this StackOverflow question with the same issue.

Also, pasting the actual error as text for SEO purpose:

MSBUILD : error MSB1009: Project file does not exist

davidebbo on Nov 21, 2016

@dannythomas13 kudu runs build command at repository root (@davidebbo maybe we should put this sentence in the document) your problem would be solved if dotnet cli knows which version to launch depending on the global.json in your project/solution directory and NOT THE CURRENT (repository root). This issue is already being tracked on github, and until then we probably don’t want to hack it ourselves in kudu.

watashiSHUN on Jun 14, 2017

@leedjones , I took a quick look at your kudu, your global.json should be put under D:\home\site\repository the same place where you put .git

watashiSHUN on Nov 18, 2016

I don’t understand what changed, but I know how you can fix it. Instead of setting PROJECT, try setting SCM_SCRIPT_GENERATOR_ARGS:

SCM_SCRIPT_GENERATOR_ARGS=--aspNetCore "FOO\src\FOO" --solutionFile FOO\FOO.sln

I replaced the name of your project by FOO here to not reveal it, so do change that.

Still trying to understand root issue, but prioritizing getting you unblocked for now.

davidebbo on Nov 18, 2016