4

I've got Visual Studio 2015 Professional installed, as well as what I should need to run and debug .NET Core code. Those packages are:

Microsoft .NET Core 1.0.0 - SDK Preview 2 (x64)
Microsoft .NET Core 1.0.0 - SDK Preview 2 (x86)
Microsoft .NET Core 1.0.0 - VS 2015 Tooling Preview 2

When I try to open an existing .NET Core app that was developed on a Mac, I get the following error popup in Visual Studio:

Visual Studio Failure Message
When I run the dotnet --version command in cmd.exe, I get the following output: 1.0.0-preview2-003121.

Am I missing some version of something? I've gone over a bunch of other posts that suggested that making sure that the DotNet CLI was uninstalled would fix this kind of problem, but I don't have it installed, and I'm still not able to get Visual Studio to correctly restore packages or build a .NET Core app.

EDIT: Here are the contents of project.json:

{
  "version": "0.1.0-*",
  "buildOptions": {
    "emitEntryPoint": true
  },
  "dependencies": {
    "Microsoft.NETCore.App": {
      "type": "platform",
      "version": "1.0.0"
    },
    "System.IdentityModel.Tokens.Saml": "5.0.0-beta8-305061149",
    "Microsoft.Extensions.Logging": "1.0.0",
    "Microsoft.Extensions.Logging.Console": "1.0.0",
    "Microsoft.Extensions.Logging.Debug": "1.0.0",
    "Microsoft.Extensions.Configuration.Json": "1.0.0",
    "Microsoft.Extensions.Configuration.EnvironmentVariables": "1.0.0",
    "Microsoft.AspNetCore.Server.Kestrel.Https": "1.0.0",
    "Microsoft.Extensions.DependencyInjection": "1.0.0",
    "Microsoft.AspNetCore.StaticFiles": "1.0.0",
    "Microsoft.AspNetCore.Mvc": "1.0.0",
    "AWSSDK.S3": "3.2.5-beta",
    "System.Threading.Tasks.Extensions": "4.0.0"
  },
  "frameworks": {
    "netcoreapp1.0": {}
  }
}
4
  • What version of the SDK does the project.json call for? Commented Jul 12, 2016 at 18:41
  • Do you have Visual Studio Update 3 ? Commented Jul 12, 2016 at 19:08
  • Yes, I installed Visual Studio Update 3 before trying all of this. Commented Jul 12, 2016 at 19:17
  • Maybe you can find this helpful: superuser.com/questions/1431833/…. It worked for me :) Commented Jul 29, 2019 at 21:02

1 Answer 1

5

For some reason, repairing Visual Studio after making sure that the Core SDK was installed fixed my problem. I guess I got things out of order when I was installing.

Sign up to request clarification or add additional context in comments.

Comments

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.