The following error occurred attempting to run the project model server process (1.0.3).

ghost commented 7 years ago

Microsoft Visual Studio

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

The project model server process provides intellisense, build, and reference information to Visual Studio and without it your experience will be very limited. Please try closing and reopening Visual Studio to see if that corrects the problem. Alternatively, check that the .NET Core SDK is properly installed.

OK

There is an issue here: https://github.com/aspnet/Tooling/issues/629, but it seems to be targeting a different version.

When rebuilding the project, following error occurs: The imported project "C:\Program Files\dotnet\sdk\1.0.3\Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.

ghost commented 7 years ago

It seems that I have multiple dotnet sdk versions installed.

However none of these folders have "Microsoft" sub folder C:\Program Files\dotnet\sdk\1.0.3\ ~~Microsoft\VisualStudio\v14.0\DotNet\Microsoft.DotNet.Props~~

mlorbetske commented 7 years ago

From the other issue, does adding a global.json (contents below) to the directory above the project make it work again?

{
  "sdk": {
    "version": "1.0.0-preview2-1-003131"
  }
}

rready commented 7 years ago

did you ever resolve this issue?

fbau3r commented 6 years ago

Experienced a similar issue after installing .NET Core SDK 1.0.4 parallel with older .NET Core SDK 1.0.0-preview2-003131 when opening an older solution with Visual Studio (Microsoft Visual Studio Community 2015, Version 14.0.25431.01 Update 3).

The two versions in directory C:\Program Files\dotnet\sdk:

The text contents of the error dialog:

---------------------------
Microsoft Visual Studio
---------------------------
The following error occurred attempting to run the project model server process (1.0.4). 

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

The project model server process provides intellisense, build, and reference information to Visual Studio and without it your experience will be very limited. Please try closing and reopening Visual Studio to see if that corrects the problem. Alternatively, check that the .NET Core SDK is properly installed.
---------------------------
OK   
---------------------------

Solution

Creating global.json in my project's parent directory with the following contents worked for me (used mlorbetske's suggestion, applied my "old" .NET Core SDK Version):

{
  "sdk": {
    "version": "1.0.0-preview2-003131"
  }
}

I don't experience the mentioned error message in Visual Studio any longer.

rready commented 6 years ago

I did that also thanks

On Aug 8, 2017 5:54 AM, "Florian Bauer" notifications@github.com wrote:

Experienced a similar issue after installing .NET Core SDK 1.0.4 parallel with older .NET Core SDK 1.0.0-preview2-003131 when opening an older solution with Visual Studio (Microsoft Visual Studio Community 2015, Version 14.0.25431.01 Update 3).

Microsoft Visual Studio

The following error occurred attempting to run the project model server process (1.0.4).

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

The project model server process provides intellisense, build, and reference information to Visual Studio and without it your experience will be very limited. Please try closing and reopening Visual Studio to see if that corrects the problem. Alternatively, check that the .NET Core SDK is properly installed.

OK

Creating global.json in my project's parent directory with the following contents worked for me (used mlorbetske's suggestion https://github.com/aspnet/Tooling/issues/1034#issuecomment-299643501, applied my "old" .NET Core SDK Version):

{ "sdk": { "version": "1.0.0-preview2-003131" } }

I don't experience the mentioned error message in Visual Studio any longer.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/aspnet/Tooling/issues/1034#issuecomment-320909126, or mute the thread https://github.com/notifications/unsubscribe-auth/AWXy5Tau8ypGn2dLnPQN3xqtLDzd_87jks5sWDBNgaJpZM4NQYU2 .

chadwixk commented 6 years ago

@fbau3r Thanks for the clarification that the global.json goes at the Project parent directory and not the Solution parent directory. In other solutions on the ye ol' interwebs it was suggested to put in a Solution Items folder at the Solution level and in that folder put the global.json file. That does work, if you have just a single project.

I was going nuts because in one sample I downloaded, it just had a single project, and the Solution level worked. Then I was downloading another sample ASP.NET Core project and trying to get it to run....this error creeped up again, but this time the solution level global.json didn't work...I was pulling my hair out!

Then I copied the global.json file and put it in the root of each project within the solution...no more error message!

aspnet / Tooling