Update DotNetCore Aliases to match tooling 1.0

With the release of VS 2017, .NET Core Tooling has been bumped to 1.0. This has introduced a new build system (move from project.json to csproj and msbuild), changes to existing commands and added additional commands. It would be nice for the DotNetCore Aliases to reflect the changes, making it easier for ppl to migrate over to the new tooling.

I asked in gitter and @gep13 said you would be willing to accept a PR on this and I am happy to put some time in to do it. However I have some questions before starting

1. Given that VS 2015 wont use v1.0 of the tooling should we continue to support Project.Json version of the tooling for the time being?
2. If we support both we will need a new set of alias to distinguish, any thoughts on how you prefer for this to be? Does the new tooling become DotNetCore* and old become DotNetCoreJson* creating a breaking change or keep current as is and new Aliases called something like DotNetCoreMSBuild*?
3. Would it be easier for review process if I split this into multiple PRs?

Tasks:

• Common Changes - ~#1549~
• Add DotNetCoreClean - ~#1555~
• Add DotNetCoreNugetPush - ~#1581~
• Add DotNetCoreNugetDelete - ~#1565~
• Add DotNetCoreMSBuild - ~#1599~
• Add DotNetCoreVSTest - ~#1675~
• Review DotNetCoreRestore - ~#1534~
• Review DotNetCoreBuild - ~#1550~
• Review DotNetCorePublish - ~#1552~
• Review DotNetCoreTest - ~#1554~
• Review DotNetCorePack - ~#1553~
• Review DotNetCoreRun - no change required
• Review DotNetCoreExecute -~#1551~
• Review if any changes required for 1.0.4 of tooling - no change required

[devlead]

@devlead RE dotnet xunit it may pay to have a generic DotNetCoreTool alias?

More than happy to put that together.

@JeremyCade Sounds like a reasonable feature to add, would you mind raising a separate issue for this, so we can track/discuss it separately and feel free to do a WIP PR if you want to.

[JonCubed]

@gep13 most of the original commands are now just wrappers for the advance commands in the new tooling.

On Mon., 17 Apr. 2017, 04:50 Gary Ewan Park, [e-mail] wrote:

@devlead https://github.com/devlead perfect! 👍

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/cake-build/cake/issues/1533#issuecomment-294471160, or mute the thread https://github.com/notifications/unsubscribe-auth/ACbHvGbJKmFGThzHGHzH5i8vuv_4yRnCks5rw1IjgaJpZM4Me6fP .