Skip to content
This repository has been archived by the owner on Apr 11, 2020. It is now read-only.

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

Open
ghost opened this issue May 4, 2017 · 6 comments

Comments

@ghost
Copy link

ghost commented May 4, 2017


Microsoft Visual Studio

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

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: #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
Copy link
Author

ghost commented May 4, 2017

It seems that I have multiple dotnet sdk versions installed.
image

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
Copy link

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
Copy link

rready commented Jun 19, 2017

did you ever resolve this issue?

@fbau3r
Copy link

fbau3r commented Aug 8, 2017

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 two most recent .NET Core SDK Versions installed on my machine

  • 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
Copy link

rready commented Aug 8, 2017 via email

@chadwixk
Copy link

@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!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants