New tooling

[galvesribeiro]

• Updated the tooling so people using VS2017 and latest released dotnet CLI can build the project again.
• Updated build scripts to match new tooling.
• Removed .nuspec files. They aren't necessary anymore with the new tooling.

[msftclas]

Hi @galvesribeiro, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!

The agreement was validated by Microsoft and real humans are currently evaluating your PR.

TTYL, MSBOT;

[galvesribeiro]

@jterry75 Hey, I've updated to the new tooling here but for whatever reason AppVeyor is not able to clone the code from GH. Can you give a hand here? I'm trying to move forward with the rest of the issues to I can use it.

[jterry75]

I dont quite understand that failure from AppVeyor. Can you rebase and push an update to get AV to try again. Seems like a node failure. We dont control that part of the clone process.

[galvesribeiro]

@jterry75 same issue... I'll open another PR from another branch and see if it happen there...

[galvesribeiro]

Ok, it doesn't work @jterry75. Can you open a ticket on AV?

Thank you.

[jterry75]

Oh I didnt look closely enough. This is a bug in your AppVeyor.yml You cant copy to $PWD because that is the folder where the git checkout takes place (hence it is no longer empty). You need to copy to c: like we used to for staging or somewhere else.

[galvesribeiro]

@jterry75 ok, fixed :)

Once we have it merged I'll look at the AutoRest thing. Thanks!

[jterry75]

Ok one more change. Can we keep passing the version number so the AppVeyor build increments like it used to. We can hard code the major.minor in the file and use .* to have appVeyor replace it

[jterry75]

$($env:appveyor_build_version)

[galvesribeiro]

Oh! right