# Using Visual Studio debugger should be supported **URL:** \ **Category:** Suggestions\ **Created:** [February 20, 2023, 3:55pm UTC](https://community.coherence.io/t/using-visual-studio-debugger-should-be-supported/229 "2023-02-20T15:55:39Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Neodamus](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Neodamus](https://community.coherence.io/u/Neodamus)\ **Post date:** [February 20, 2023, 3:55pm UTC](https://community.coherence.io/t/using-visual-studio-debugger-should-be-supported/229/1 "2023-02-20T15:55:40Z")
If trying to use Debugger in Visual Studio, the connection will die and create errors if staying at a breakpoint for more than a few seconds. It seems like there is some built-in keep-alive system for the connection, but ideally there would be an option to disable this in development. ---
**Author:** ![ciro](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/ciro/32/82_2.png) [@ciro](https://community.coherence.io/u/ciro)\ **Post date:** [February 22, 2023, 10:31am UTC](https://community.coherence.io/t/using-visual-studio-debugger-should-be-supported/229/2 "2023-02-22T10:31:34Z")
If you go inside Unity’s **Project Settings** \> **Player** \> **Resolution and Presentation** , do you have **Run in Background** enabled? Also check **Project Settings** \> **coherence** \> **Keep connection alive (Editor only)** Does it still happen then? ---
**Author:** ![Neodamus](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Neodamus](https://community.coherence.io/u/Neodamus)\ **Post date:** [February 22, 2023, 3:45pm UTC](https://community.coherence.io/t/using-visual-studio-debugger-should-be-supported/229/3 "2023-02-22T15:45:39Z")
I had the “Run In Background” option already enabled. I did enable the “Keep connection alive” setting after reading this, but it did not seem to resolve the issue. I put a breakpoint in my sim script when it gains authority, just for testing, and left it at the breakpoint for 1minute, then continued. After that, I encountered the highlighted errors and connection was lost: [http://sc.com.ly/show/6c88da24-3377-4c67-abe0-c9d5eeb8a62d](http://sc.com.ly/show/6c88da24-3377-4c67-abe0-c9d5eeb8a62d) ---
**Author:** ![ciro](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/ciro/32/82_2.png) [@ciro](https://community.coherence.io/u/ciro)\ **Post date:** [February 23, 2023, 10:50am UTC](https://community.coherence.io/t/using-visual-studio-debugger-should-be-supported/229/4 "2023-02-23T10:50:32Z")
Interesting. And just as a final thing, the Room was still there? In the Dashboard, you can choose a timeout for your Rooms to close them after inactivity. Is it set very low? The URL: [https://coherence.io/dashboard/[your-org]/[your-project]/rooms](https://coherence.io/dashboard/%5Byour-org%5D/%5Byour-project%5D/rooms) **EDIT:** nevermind, sorry, I saw that you mentioned in another thread that local Rooms stay active for up to 10 minutes. Looks like something we need to look at, thanks for the reminder! ---
**Author:** ![per\_coh](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/per_coh/32/27_2.png) [@per\_coh](https://community.coherence.io/u/per_coh)\ **Post date:** [July 8, 2024, 10:22am UTC](https://community.coherence.io/t/using-visual-studio-debugger-should-be-supported/229/5 "2024-07-08T10:22:13Z")
@Neodamus is this still relevant? ---
**Author:** ![Neodamus](https://avatars.discourse-cdn.com/v4/letter/n/4491bb/32.png) [@Neodamus](https://community.coherence.io/u/Neodamus)\ **Post date:** [July 9, 2024, 1:52pm UTC](https://community.coherence.io/t/using-visual-studio-debugger-should-be-supported/229/6 "2024-07-09T13:52:22Z")
This is still an issue. I’m not aware of any way to use the debugger in networked setting without killing the connection. After staying at a breakpoint for a few seconds, the connection ends. ---
**Author:** ![miguel-coherence](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/miguel-coherence/32/101_2.png) [@miguel-coherence](https://community.coherence.io/u/miguel-coherence)\ **Post date:** [July 10, 2024, 7:48am UTC](https://community.coherence.io/t/using-visual-studio-debugger-should-be-supported/229/7 "2024-07-10T07:48:20Z")
Hello, this is a known issue on our end, the keep connection alive setting doesn’t work properly when using Rooms. Sorry for the inconvenience. ---
**Author:** ![Filip](https://dub1.discourse-cdn.com/flex017/user_avatar/community.coherence.io/filip/32/142_2.png) [@Filip](https://community.coherence.io/u/Filip)\ **Post date:** [September 17, 2024, 11:17am UTC](https://community.coherence.io/t/using-visual-studio-debugger-should-be-supported/229/8 "2024-09-17T11:17:57Z")
The fix for this issue has shipped in the just-released version [1.3.0](https://docs.coherence.io/v/1.3/support/release-notes)