Answered by:
MSBuild 14 and ASP.Net Core web app

Question
-
Hi,
I am currently using an ASP.NET Core ap using .csproj instead of project.json. (Tooling preview 4)
Azure gives me:
"Nothing to do. None of the projects in this solution specify any packages for NuGet to restore."
I believe this might be from Azure using MSBuild 14 over 15, so it's not accepting the lack of project.json (or packages.config).
- Edited by Jme Saunders Wednesday, November 30, 2016 10:55 PM
Wednesday, November 30, 2016 10:49 PM
Answers
-
Hello:
I believe this message shows up when running "nuget3.5 restore" against a preview4 dotnet core project. How are you deploying to azure? can you paste here the entire error message? currently, the easiest way of getting a preview4 project(although azure web only have preview3 cli tools) to run in azure is through this:
SCM_SCRIPT_GENERATOR_ARGS=--aspNetCore "csproj file path" --solutionFile "solution file path"
please refer to this [documentation](https://github.com/projectkudu/kudu/wiki/Configurable-settings#taking-over-the-script-generator-command-line) for usage
- Proposed as answer by AjayKumar-MSFTMicrosoft employee, Owner Thursday, December 1, 2016 8:50 AM
- Marked as answer by Jme Saunders Friday, December 2, 2016 10:16 PM
Thursday, December 1, 2016 12:56 AM
All replies
-
Hello:
I believe this message shows up when running "nuget3.5 restore" against a preview4 dotnet core project. How are you deploying to azure? can you paste here the entire error message? currently, the easiest way of getting a preview4 project(although azure web only have preview3 cli tools) to run in azure is through this:
SCM_SCRIPT_GENERATOR_ARGS=--aspNetCore "csproj file path" --solutionFile "solution file path"
please refer to this [documentation](https://github.com/projectkudu/kudu/wiki/Configurable-settings#taking-over-the-script-generator-command-line) for usage
- Proposed as answer by AjayKumar-MSFTMicrosoft employee, Owner Thursday, December 1, 2016 8:50 AM
- Marked as answer by Jme Saunders Friday, December 2, 2016 10:16 PM
Thursday, December 1, 2016 12:56 AM -
Thank you very much!
That was indeed the problem and I got it sorted quite quickly.
Friday, December 2, 2016 10:17 PM -
Hello:
I have good news, Azure just pushed an update to support projects created with latest dotnet tooling, you don't need SCM_SCRIPT_GENERATOR_ARGS=--aspNetCore "csproj file path" --solutionFile "solution file path" anymore, you can deploy your project as is, let me know if you run into troubles doing that
Saturday, December 3, 2016 12:12 AM