MSB4126 error when executing dotnet restore about examples HOT 13 CLOSED

Updated to use the latest VS build tools.

from examples.

What's the solution?

from examples.

The solution is to update your checkout because I updated the code to use the latest VS build tools, thus removing the issue.

from examples.

What is a checkout? I am using VS2017...

from examples.

• If you cloned the GitHub repo to get the code, just do a git pull to update your checked out copy of the code ("your checkout").
• If you manually downloaded the code as a zip file instead, do a new download.

from examples.

Ah, ok I understand, we call it "Get Latest".
I did a new download. But same error.

from examples.

• Shut down all VS instances.
• Remove all your .vs, bin, and obj folders (or do git clean -dfx)
• Make sure you have all the VS patches up to current.

I can't reproduce any errors anymore and it builds fine on AppVeyor as well, so I'm not sure what more guidance I can provide. It's going to be a per-user / environment-specific problem if that doesn't fix it.

from examples.

It's only the ASP.NET Core project that is failing....

from examples.

I did what you said, but dotnet restore failed, I executed the build.ps1 file, you can see the result above.
Thanks for the quick support!

from examples.

As mentioned, I can't reproduce this either on any local machine I have or on the AppVeyor continuous integration build server. That means it's something with your machine or your user account/profile on that machine that I'm not able to troubleshoot. If I can't repro it, I can't do anything further to help. Sorry.

You could try additional troubleshooting on your end. For example...

• Create a brand new ASP.NET Core web app. File => New style. Do a diff and see what's different between the example project and the file/new project you just made.
• Run nuget at the command prompt. It should be a really recent version, something in the 4.3 - 4.4 range. 2.x or early 3.x doesn't know how to handle package restore right.
• Do a dotnet --version from the command prompt. It should show 1.1.0. If it doesn't, that's a problem - it's not obeying the global.json.
• Did you switch your NuGet sources? The NuGet.config in the Examples repo points at nuget.org by default, some enterprises or devs set up their own settings.
• Clear your NuGet package cache: nuget locals all -clear

At this point I'm really just grasping at straws because, again, I can't reproduce the issue at all anywhere. If you still can't figure it out, consider opening a question on StackOverflow so you have a wider audience to help you - there are only maybe two people who watch this repo, one of whom is me. There are thousands of people to help you on StackOverflow.

from examples.

I tried all the things except the Diff, with no luck!

I have opened an thread regarding this issue on SO.

from examples.

I migrated the project to .net core 2.0 and changed the global.json to point to sdk 2.1.3.
Removed all references in AspNetCoreExample manually and added the latest version for all of them.
Now it works.

from examples.

I solved it by canceling the environment variable Platform: SET Platform=

from examples.