NuGet / Home

Repo for NuGet Client issues
Other
1.49k stars 250 forks source link

Ctrl+C in PMC does not close an app started via dotnet.exe run #6887

Open rohit21agrawal opened 6 years ago

rohit21agrawal commented 6 years ago

From email thread;

A customer is trying to use the .NET Core CLI from the Package Manager Console window in the latest release of VS 2017. When he executes “dotnet run” from the project root in his ASP.NET Core 2.0 MVC project, he’s unable to kill the process by pressing Ctrl + C. This should work, and I was able to reproduce it in 15.7 Preview 5.

Shilpishabdita commented 6 years ago

<3

bensongathee commented 5 years ago

Is there any resolution to this issue? I have to restart my laptop each and everytime I run the "dotnet run" command on my laptop

Rick-Anderson commented 5 years ago

@bensongathee

Is there any resolution to this issue?

bensongathee commented 5 years ago

@Rick-Anderson what's the name of the .NET Core Host in task manager. Can't seem to locate it

Rick-Anderson commented 5 years ago

image

Rick-Anderson commented 5 years ago

The exe is dotnet.exe, but there are usually alot of those.

bensongathee commented 5 years ago

@Rick-Anderson works perfectly. Thanks you sir. Appreciate it

bensongathee commented 5 years ago

@Rick-Anderson I've been using dotnet run command on PMC to run my Application in ASP.NET Core Web Application, but then switched to ASP.NET Web Application(.NET Framework) but it doesn't work. Any recommendations on how I can use dotnet run command to run my application in ASP.NET Web Application(.NET Framework)?

elgunaliyev commented 5 years ago

PCM after command "dotnet run" can't exit just by pressing Ctrl+C In VS2019. Only way kill service from Task Manager.

Raevenn commented 1 month ago

Since the past few months I've been running into the same issue. I run dotnet watch run --launch-profile "ourProfileName", it runs perfectly but the moment it is running I can no longer shut it down using CTRL + C. I have to manually close the CLI and run a new window and re-run the command.

Very frustrating that this is still an issue since 2018 and has been put in the"icebox", but its weird that it only popped up recently for me.