46
votes

I'm getting this error when opening .NET Core projetcs in VS 2015 Community:

The following error ocurred attempting to run the project model server process (1.0.0-preview-003585).

Unable to start the process. No executable found matching command "dotnet-projectmodel-server".

It was working well until yesterday. I've already tried do reinstall the .NET Core SDK and repair the VS installation.

Some tips?

9
Are you running Update 3 of visual studio 2015?Muqeet Khan
@MuqeetKhan, yes I am.rsilva
I got this error after I installed latest dev version of CLI dotnet-dev-win-x64.latest.exe. No solution yet.CrnaStena
I'm getting this error now. It started after I installed the RC version of Visual Studio 2017.Rob Lyndon

9 Answers

55
votes

I had this same problem. I was able to fix it by uninstalling Microsoft .NET Core 1.0.1 - SDK Preview 3 (x64) and reinstalling the .NET Core 1.1 SDK from here:

https://www.microsoft.com/net/core#windowscmd

32
votes

Another option to fix this is to add a Solution folder called "Solution Items" and add a global.json file in it with an "sdk" element specifying the correct SDK version if you have multiple installed side-by-side. I installed 2017 RC and I started getting this error because it installs Preview 4. I don't want to uninstall Preview 4 or 2017 will stop working. Adding the global.json file with the following text fixed it for me. (check your %PROGRAMFILES%\dotnet\sdk folder for installed SDK versions.)

{ "sdk" : { "version" : "1.0.0-preview2-1-003177" } }
13
votes

Update (11 May, 2017)

According to the new Announcing .NET Core Tools 1.0 blog post:

We’re now encouraging everyone to migrate to MSBuild and csproj from project.json. As I stated above, we will not be supporting any of the new .NET Core tools in Visual Studio 2015. We also won’t be updating the Visual Studio 2015 project.json-based tools.

Original answer

There is a closed issue related to this problem in the .NET Core CLI repo:

Unable to start process "dotnet-projectmodel-server" while starting VS2015

According to the post Changes to Project.json, since Preview 3 the .NET Core tooling moved from .xproj/project.json to .csproj/MSBuild. So basically you have three choices:

  1. Continue using the .xproj/project.json format with a Preview 2 SDK (as said in @Tim Schmidt's answer)

  2. Use the dotnet migrate tool or the VS 2017 RC to migrate your existing project.json assets to csproj. Note that if you are using VS 2015, you will lost the .NET Core Tooling until the VS 2015 Tools (Preview 2) is updated.

  3. Work with project.json and csproj on the same machine, switching between the Preview 2 and Preview 3+ with the help of the global.json file (as said in @randcd's answer).

But, if you plan to migrate to .csproj/MSBuild, pay attention to the post Using MSBuild to build .NET Core projects:

We recommend that most people targeting .NET Core with new projects today use the default tooling experience with project.json because of the following reasons:

  • MSBuild doesn't yet support a lot of the benefits of project.json
  • A lot of the ASP.NET based tooling doesn't currently work with MSBuild projects
  • When we do release the .NET Core tooling that uses MSBuild, it will be able to automatically convert from project.json to MSBuild projects
7
votes

I got this message when I was trying out a new Angular2 with .NET Core template from the ASP.NET Core Template Pack.

Basically, you'll need a global.json file as a Solution Item in the Solution folder (NOT Projects)

{
  "projects": [ "src", "test" ],
  "sdk": {
    "version": "1.0.0-preview2-003131"
  }
}

For more information, you can read further on this page.

Dot Net Core Tutorials

2
votes

In my case, after installing .net core 1.1.0 there were still versions 1.0.1 installed. Delete old versions and reinstall Microsoft .NET Core tools.

1
votes

I got the same error after installing .Net Core 1.0.1 (x64) on Visual Studio 2015 Enterprise following these steps:

  1. Installed .Net Core SDK 1.0.1
  2. Opened Visual Studio, Went to Tools, Extensions and Updates and saw there was an update for Asp.Net and Web Tools which I chose to to install

I tried to fix it by uninstalling and re-installing the latest version of .Net Core SDK but that didn't solve my problem. I kept getting the error:

fig 1. error dialog

In my case, I was trying to create a new project using a custom template, so I changed and tried to create a new Asp.Net Core Web Application (.Net Framework) and I got an error that told me exactly what version of the .Net Core SDK I needed:

fig. 2. Dialog indicating the version of SDK

I followed the link from the dialog (click here or go here: https://github.com/aspnet/Tooling/blob/master/known-issues-vs2015.md#missing-sdk) and downloaded the specific version. I Uninstalled the current .Net Core SDK (1.0.1 x64), then installed the suggested one (1.0.0-preview2-003131 in my case) and that fixed my problem.

1
votes

I has that problem after installing visual studio 2017, I just created a global.json file with this configuration:

{
  "projects": [ "src", "test" ],
  "sdk": {
    "version": "1.0.0-xxxxx"
  }
}

To know which version you are possibly using, open your console and go to C:\Program Files\dotnet\sdk> then execute a simple dir command, that will list the folders of the different dot net core versions you may have on your system, try one by one and select the version that works for you.

BTW: it worked for me to place the global.json in the project root, not the solution.

0
votes

I just encountered the same issue after updating Microsoft Azure SDK v2.9.6

I uninstalled the 2.9.6 SDK and noticed I had a problem opening my global.json file. So I got the most recent version from VSTS for my solution and that fixed my problem.

-2
votes

Not a good position at all. Dot Net Core 1.0 is the LTS version and this is the one to target. .NET Core 1.1 is NOT the LTS version (and will not run on Amazon for example). So recommending this route goes against Microsoft's policy on LTS versions.

An LTS version MUST continue to be "supported for three years after the general availability date of a LTS release"