c#asp.net-coreasp.net-core-webapivisual-studio-2019.net-core-2.2

Reputation: 5248

The target process exited without raising CoreCLR started event error with .NET Core 2.2

I want to debug an empty WebApi Project based on .NET Core 2.2.

I installed the "Core 2.2 SDK x86" and changed the target framework to 2.2:

<Project Sdk="Microsoft.NET.Sdk.Web">
  <PropertyGroup>
    <TargetFramework>netcoreapp2.2</TargetFramework>
  </PropertyGroup>

When I started to debug this project, IIS starts, but in the route api/values I see nothing (it loads forever) and I get this error:

The target process exited without raising a CoreCLR started event.Ensure that the target process is configured to use .NET Core. This may be expected if the target process did not run on .NET Core

In my solution WPF and Class Library projects exist. I wanted to make a WebApi for it. Like I said, it's an empty base project generated by Visual Studio 2019. I just installed Core 2.2. Why do I get that error and what am I doing wrong?

Upvotes: 101

Answers (30)

IS4

Reputation: 13217

In my case, the application had run but Visual Studio thought it exited. In the end the reason was VxKex was accidentally enabled on the target executable, which made VS pick its loader instead of the program itself when debugging.

This is probably a very minor cause, but in case something like this is happening as a result of this or other IFEO-based programs, using Process Monitor to see what processes are created by VsDebugConsole.exe might help.

Upvotes: 0

Roger

Reputation: 1082

It happened to me while upgrading .Net Core 5 project to .Net Core 6.

The project was running in Docker.

I forgot to point to the right image in the multi-stage Dockerfile like:

FROM mcr.microsoft.com/dotnet/aspnet:6.0 AS base

and

FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build

Targeting aspnet:5.0 and sdk:5.0 causes the error:

The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use .Net Core. This may be expected if the target process did not run on .Net Core.

Upvotes: 5

Skyfish

Reputation: 147

I removed .NET Core from Target Frameworks, leaving .net462.

Upvotes: 0

RuhrpottDev

Reputation: 564

I got this message while running an web application with script debugging enabled and got this message:

In the output tab, I got also the following message:

The target process exited without raising a CoreCLR started event. Ensure that the target process is configured to use .NET Core. This may be expected if the target process did not run on .NET Core.The program '[75680] dotnet.exe' has exited with code 2147516566 (0x80008096).

Solution for me:

Open the Visual Studio Installer, install the newest update. No windows restart needed in my situation. That was all. Simple.

As you can see from other answers: Solution could be different for everybody, but the problem has something to do with uninstalled things. The question is: What you are missing.

Upvotes: 0

CamiloVA

Reputation: 731

To me it happened after I rename the project name and also rename the AssemblyName.

I solved it removing hidden folder .vs and obj, both located inside project's directory. Then reload or reopen the project on VS.

I cant now debug with Any Cpu again.

Upvotes: 0

RadicalGratitude

Reputation: 425

This error occurred when I tried changing C# projects in my solution to use Docker and running it:

The error went away when I changed the C# projects back to use the Visual Studio's debug server and running it:

Upvotes: 1

Rafik Samman

Reputation: 11

I've encountered this issue multiple times, using VS 2017 and VS 2019 across .NET Core 2.1, 3.1 and 5.0.

There are many conditions that can cause this problem to occur:

Microsoft Update can install a version of .Net Core at any time, automatically and outside of your awareness and knowledge.

It can also change the installation of any .Net Core SDK version's installed components.

Your version of VS has to be compatible with the version of the .Net Core SDK that you have installed.

You must have all of the following components installed for this error to be resolved/pre-empted for .NET 5.0 (please check the dotnet 5.0 site for the compatibility list by versions).

Microsoft .NET SDK 5.0.408 which includes (the following below) must all be installed and listed in the control panel: .NET Core 5.0.17 Windows Desktop Runtime,.NET Runtime, Windows Server Hosting, Shared Framework

If any .NET Core 3.1 SDK are installed without your knowledge, you must uninstall it and repair your targeted .net core version's installation.

Upvotes: 0

mohamed saeed

Reputation: 303

I see many answers like try and error after searching about the issue, I got the following : it simply depends on three parameters and they have to be compatible

Windows platform "x86,x64" you can change it from the CPU option of the visual studio or choose any CPU hence the install .net x framework should be compatible with the windows
The target framework for the project (check the project target framework "right-click on the project and check target framework") if it is 5 so the enabled in the third parameter should be 5 or change this one but take care you should tell the other team members if you change it
The Enabled framework go for tools and get tools and go for individuals component and chose the target framework the same as found in step 2 and press modify

Upvotes: 5

Pedro Lizondo

Reputation: 11

I had same issue. Now in VS2022 you cannot download NetCore2.2. So just download and install NetCore 2.2 from microsoft dotnet website. https://dotnet.microsoft.com/en-us/download/dotnet/2.2

Upvotes: 1

IAmAgainst

Reputation: 23

I started to get this error after updating Visual Studio from 2019 to 2022. It turned out that the project target framework was set to .Net Core 3.1, which was removed when I uninstalled VS2019, and the solution was to change it to .Net 6.0 which is the component I had selected during installation (Installing .Net Core 3.1 from the Visual Studio Installer should work as well).

To do so, right click on the project name and look for the "Target framework" option (my installation is in Spanish so that's what I presume it should say).

Upvotes: 0

Eric Berridge

Reputation: 41

For me, I'd just installed Visual Studio 2022 on a fresh installation of Windows 11. My project uses .Net 5, which wasn't installed by default (I only had .Net 6). I simply used the Visual Studio installer, modified my VS2022, selected Individual Components, and enabled .Net 5. Viola!

Upvotes: 0

Bazil

Reputation: 506

I ran with the same problem. But for me it was that my project was running in .NET Core 2.2, which I didn't have installed. I'm using VS 2019.

So for the solution, just go to Visual Studio Installer and for your VS 2019 hit "Modify" like in the following image (it's in spanish though): See image here

Then, click "Individual Components", like here.

And then, make sure you checked in ".NET Core 2.2 Runtime (EOL)" (and above like .NET Core 3.0, if you want) and click "Modify", as shown here

Hope this works for you.

Upvotes: 26

Fuzzy Analysis

Reputation: 3188

In the Test Explorer window of Visual Studio 2019, make sure that there are no references to any *.testsettings or *.runsettings files if you are not using them intentionally. I had referenced a *.testsettings file unintentionally, and that was causing the issue.

Upvotes: 0

miapuffia

Reputation: 41

Since I don't see it here yet, here's what worked for me. I have a UWP project, Win32 project, and Windows application packaging project in the same solution. Running the Win32 app using FullTrustProcessLauncher.LaunchFullTrustProcessForCurrentAppAsync was giving this message and not working.

What fixed it was changing a setting in the packaging project's project settings: Debug -> Debugger type -> Background task process: Native Only

Upvotes: 2

Jeffrey Davis

Reputation: 86

A corrupt layout is also possible, had this happen myself. To fix, go to projpath\bin\x64\configtype\AppX, for example:

C:\Users\Foo\Documents\Visual Studio 2019\projectname\bin\x64\Debug\AppX

Delete everything here, rebuild and you're good to go.

Upvotes: 1

JWP

Reputation: 6963

VS2019 16.7.1 ASP.Net Core 3.1

Our Nunit test projects that issued this error, only worked with a very select set of Nunit and Microsoft packages.

Microsoft.NET.Test.sdk - 16.5
Nunit - 3.12
Nunit3TestAdapter 3.16.1

But here's the catch, you have to go into c:\users\yourname\.nuget\packages and look for all three folders shown above. If you find any other version in those folders, delete it.

I found two versions in the Microsoft.NET.Test.SDK folder. I suspect the newer version was being loaded. Why? Because when I deleted it everything ran fine.

Upvotes: 1

Toby Smith

Reputation: 1605

It seems like there are lots of different causes for this. For me, it was because I had upgraded a .csproj file but I hadn't updated the image used in my docker file.

Upvotes: 17

zed101

Reputation: 323

Faced this issue during xUnit testing. Downgrading nuget package "Microsoft.NET.Test.Sdk" to 15.9.0 worked for me

Upvotes: 3

Luke

Reputation: 344

.Net Core 2.2 is required to be installed. I fixed when I added this in Visual Studio Installer.

Upvotes: 1

John Dyer

Reputation: 2368

I had this issue and finally tracked it down to doing a "publish" operation with a deployment mode of: "Self contained" That resulted in dropping all .NET runtime binaries in my bin directory. Where I think things got totally messed up is I have several solutions all using that same common bin directory, each build different exe's and dll's. Only one was for a self contained deployment as a test. I think that started mixing up some of the minor dlls for the .NET core and causing this issue. Once I purged all the dll's that were "not mine" and rebuilt things started working again. I'm using Visual Studio 2019 16.8.2 / .NET Core 3.1

I realize the original question is regarding .NET Core 2.2 but this question comes up first when searching for the main issue.

Upvotes: 1

Nazariy Perepichka

Reputation: 521

I had the same issue.
I ran Program.cs file from the command line and the error message was different.
So, apparently, I didn't have the appropriate .NET Core runtime installed.

You can download it by the following link - https://dotnet.microsoft.com/download

Upvotes: 51

mattylantz

Reputation: 356

Be sure to install the exact version of .net core that you want your project to run on

Upvotes: 1

CodingYourLife

Reputation: 8626

Deleting all bin folders of my solution
building everything again did the trick for me

(.NET Core 3.1 VS 2019)

Upvotes: 4

Josh Graham

Reputation: 153

I was getting a similar error with my project: The target process exited without raising a CoreCLR started event.

My startup project was targeting multiple frameworks: netstandard2.0;netcoreapp2.2

I fixed this issue by changing my target framework from netstandard2.0 to netcoreapp2.2 using the following stackoverflow directions: How to switch between target frameworks for .NET Core projects in Visual Studio

Upvotes: 1

Annunaki_Selva

Reputation: 81

I have downgraded "Microsoft.AspNetCore.App" version and error gone .

Upvotes: 4

David Castro

Reputation: 1975

I was trying to run a project that used net core 2.2 but I didn't have it, and there was no error(I had 1.1), so after installing the 2.2 using the "Visual Studio Installer" it worked like a charm. =)

Upvotes: 2

maxisam

Reputation: 22745

In my case, switching to x64 save the day. enter image description here

Upvotes: 10

Enrico

Reputation: 3471

I had to do a "clean" and "rebuild" of the project and after that it worked again.

Upvotes: 30

Vlad Hrona

Reputation: 427

I had same issue after package upgrading. You don't need any vs update. Just go to dotnet.microsoft.com/download/dotnet-core/2.2 and get runtime dotnet-hosting-2.2.7-win.

Upvotes: 5

Anonymous Creator

Reputation: 3819

All of a sudden it stopped working. For me clean solution and re-build solution worked.

Upvotes: 1

The target process exited without raising CoreCLR started event error with .NET Core 2.2

Answers (30)

Related Questions