7

I've had this problem since this morning and have tried various options, but haven't found a solution to my problem yet.

The problem is that every time I want to start my Blazor web application I get this error message:

I tried several ways to solve this problem, however all I found was for IIS-Express with this problem. I use several startup projects, and I don't find any solution for my problem.

Dharman
  • 30,962
  • 25
  • 85
  • 135
Impi
  • 81
  • 1
  • 5
  • 1
    Does this answer your question? [Process with an ID #### is not running in visual studio professional 2013 update 3](https://stackoverflow.com/questions/26424902/process-with-an-id-is-not-running-in-visual-studio-professional-2013-update) – GSerg Jun 15 '22 at 07:39
  • No, unfortunately not, the problem is that the project there is always started with IIS Express and I have tried the solutions there, but unfortunately they didn't work for me because I use several start projects. – Impi Jun 15 '22 at 07:45

12 Answers12

7

I had the same problem this morning after updating the Microsoft packages in my WASM-project. Updating Microsoft.AspNetCore.Components.WebAssembly.DevServer 6.0.8 to 6.0.9 resulted in the error mentioned. Updating to .NET 6.0.109 SDK solved this. So in general: after updating the DevServer package you need to be sure you have the corresponding .NET SDK version (or higher) installed.

I'm using VS 2022 17.4.0 preview 1.0.

Michel de Kok
  • 86
  • 1
  • 2
3

Had an same issue when testing a Blazor app, it fixed after restored the package Microsoft.AspNetCore.Components.WebAssembly.DevServer from 6.0.8 to 6.0.5

Bonelol
  • 526
  • 6
  • 13
2

Just do this steps:

  1. Close Visual Studio.
  2. Navigate to the sub-folder of Project's main folder.
  3. Delete .vs folder and open project again in Visual Studio and RUN

if don't work just click on build button in app bar in visual studio then click on Rebuild Solution and run

khaldoun badreah
  • 108
  • 6
2

This solved it for me

https://www.codeproject.com/tips/1029540/solved-process-with-an-id-of-is-not-running

Open the .csproj file, and remove tags DevelopmentServerPort, DevelopmentServerVPath and IISUrl.

Edwin
  • 733
  • 8
  • 20
1

After I installed Visual Studio again it worked.

Dharman
  • 30,962
  • 25
  • 85
  • 135
Impi
  • 81
  • 1
  • 5
  • I updated the .NET SDK in my project before I updates Visual Studio. Updating VS solved the issue for me (for the next person having this issue: try this before reinstalling VS) – user3079834 Jan 13 '23 at 18:49
1

Had the same issue. Updating Visual Studio and the .NET SDK fixed it for me. I had SDK version 6.0.302 installed and updated to SDK version 6.0.400.

sveinungf
  • 841
  • 1
  • 12
  • 22
1

I had the same issue today; I updated my Blazor WASM project's nuget packages to the latest version but didn't update Visual Studio. After updating Visual Studio, this started working again. So try updating VS if you encounter this.

fverhoef
  • 11
  • 1
1

I had the same issue this morning. My project was targeting .NET Core 3.1 and I had installed the SDK. After I installed the targeting pack, everything worked fine.

Go to the Visual Studio Installer and Modify your VS. Go to individual components and search for the .NET version you are using (Core 3.1 for me) Make sure the targeting pack is installed.

enter image description here

Brian Tompsett - 汤莱恩
  • 5,753
  • 72
  • 57
  • 129
Wovi10
  • 13
  • 1
  • 3
0

I had this issue with code I downloaded from GitHub. The projects targetted .NET Core 3.1 which I hadn't installed. To solve, I double-clicked Properties in each project, and changed the Target framework to .NET 6.0.

GerardF
  • 133
  • 1
  • 2
  • 8
0

I had to delete the .vs folder as mentioned by others, but then went to the project properties and changed my framework version from 3.1 to 7.0, and rebuilt and it fixed the problem.

Ben
  • 1,169
  • 3
  • 17
  • 27
0

"Process with an id xxxx is not running"

The error is quite misleading actually. You should check in the VS Output window the exact details. In my case I had

"The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use .NET Core"

Once I saw this error double checked the .NET versions of all my projects in the solution and turned out one of them is .NET Core 2.2, which is not present on my machine.

The simple solution after I found out what is missing was to install the .NET Core 2.2 SDK and it worked!

ppenchev
  • 127
  • 1
  • 10
0

I had the same issue and once I updated Visual Studio, that solved the problem.

JT-3
  • 1
  • 2