# ASP.NET Core Project in Water can't run (debug) successfully a second time
**URL:** https://talk.remobjects.com/t/asp-net-core-project-in-water-cant-run-debug-successfully-a-second-time/26260
**Category:** Water
**Tags:** net-core, mercury
**Created:** [February 27, 2022, 5:13pm UTC](https://talk.remobjects.com/t/asp-net-core-project-in-water-cant-run-debug-successfully-a-second-time/26260 "2022-02-27T17:13:48Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@avonelle](https://talk.remobjects.com/u/avonelle)
#### Post date: [February 27, 2022, 5:13pm UTC](https://talk.remobjects.com/t/asp-net-core-project-in-water-cant-run-debug-successfully-a-second-time/26260/1 "2022-02-27T17:13:48Z")
Water v11.0.0.2717
I’m probably doing something wrong here, but when I try to “Run” my [ASP.NET](http://ASP.NET) Core MVC/Razor-based Web Application, it works fine the first time, but the second time it can’t get past “Starting [ProjectName]” in the upper right corner. Also at this point, using “Stop” doesn’t seem to work - the menu option stays active even after clicking on it like there is still something to stop.
It doesn’t seem to make a difference if I leave the browser open or closed after stopping debugging. It also doesn’t seem to matter if I Stop first then close the browser or vice versa.
I don’t know that it matters, but Firefox is my default browser on this machine.
Here’s a quick video showing the behavior:
I included the Task Manager view in case that is helpful. What I’ve found is that if I close Water and then kill any extra RemObjects.Elements.Debugger.exe tasks, then when I restart Water most of the time it works okay again.
Suggestions with a solution that doesn’t involve restarting Water each time would be greatly appreciated.
–Avonelle
---
### Author:  [@RemObjectsSoftware](https://talk.remobjects.com/u/RemObjectsSoftware)
#### Post date: [February 28, 2022, 1:11pm UTC](https://talk.remobjects.com/t/asp-net-core-project-in-water-cant-run-debug-successfully-a-second-time/26260/2 "2022-02-28T13:11:35Z")
Logged as [bugs://E25720](https://www.remobjects.com/portal/bugs/?id=E25720).
---
### Author:  [@mh](https://talk.remobjects.com/u/mh)
#### Post date: [February 28, 2022, 1:12pm UTC](https://talk.remobjects.com/t/asp-net-core-project-in-water-cant-run-debug-successfully-a-second-time/26260/3 "2022-02-28T13:12:12Z")
Out of curiosity: does the same happen for you for _any_ .NET Core project, or only [ASP.NET](http://ASP.NET)?
---
### Author:  [@avonelle](https://talk.remobjects.com/u/avonelle)
#### Post date: [February 28, 2022, 1:59pm UTC](https://talk.remobjects.com/t/asp-net-core-project-in-water-cant-run-debug-successfully-a-second-time/26260/4 "2022-02-28T13:59:33Z")
Hmmmmm…not consistently, at least with a console application I just tried.
Maybe it is something weird about my environment?
I did just try a reboot of the computer in case there was something strange going on, but that did not make a difference.
I am finding now if I kill a RemObjects.Elements.Debugger.exe process in Task Manager, it seems to “continue” and start debugging, so that isn’t so bad. Just a bit weird.
FYI - certainly not an emergency for me. I’m just trying to learn some things.
–Avonelle
---
### Author:  [@mh](https://talk.remobjects.com/u/mh)
#### Post date: [February 28, 2022, 2:41pm UTC](https://talk.remobjects.com/t/asp-net-core-project-in-water-cant-run-debug-successfully-a-second-time/26260/5 "2022-02-28T14:41:30Z")
> [@avonelle](#):
>
> I am finding now if I kill a RemObjects.Elements.Debugger.exe process in Task Manager, it seems to “continue” and start debugging, so that isn’t so bad. Just a bit weird.
Curious. Can you find out if that Debugger.exe is left of from the _first_ session thats stuck (ie it sticks around after debugging finished), or is it the freshly launched one from the second session that gets stuck?
---
### Author:  [@avonelle](https://talk.remobjects.com/u/avonelle)
#### Post date: [February 28, 2022, 2:52pm UTC](https://talk.remobjects.com/t/asp-net-core-project-in-water-cant-run-debug-successfully-a-second-time/26260/6 "2022-02-28T14:52:58Z")
It is the debugger.exe left from the previous session that sticks around after debugging finishes. Ending the task in Task Manager restarts it (with a new process ID), probably because Water is trying to start the debugging process.
–Avonelle
---
### Author:  [@RemObjectsSoftware](https://talk.remobjects.com/u/RemObjectsSoftware)
#### Post date: [March 8, 2022, 6:57am UTC](https://talk.remobjects.com/t/asp-net-core-project-in-water-cant-run-debug-successfully-a-second-time/26260/7 "2022-03-08T06:57:54Z")
[bugs://E25720](https://www.remobjects.com/portal/bugs/?id=E25720) was closed as fixed.