hiddentn/dotnet-debugger — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2023-05-28
Connect Visual Studio or JetBrains Rider to a remote .NET container to set breakpoints and inspect variables.
Track down memory leaks in a remote environment using the included dotMemory tool.
Capture performance traces from a production-like container using dotTrace.
Standardize debugging environments across a team deploying .NET apps in containers.
| hiddentn/dotnet-debugger | brandur/heroku-buildpack-mono-build | chrisor-dev/claude-autosync | |
|---|---|---|---|
| Stars | 2 | 2 | 2 |
| Language | Shell | Shell | Shell |
| Last pushed | 2023-05-28 | 2012-01-27 | — |
| Maintenance | Dormant | Dormant | — |
| Setup difficulty | hard | moderate | moderate |
| Complexity | 4/5 | 2/5 | 3/5 |
| Audience | developer | ops devops | developer |
Figures from each repo's GitHub metadata at analysis time.
Documentation is still work-in-progress (WIP), and setup requires Docker plus a remote or cloud server.
Pre-built Docker containers that let you remotely debug .NET apps with Visual Studio or JetBrains Rider, plus memory and performance profiling tools.
Mainly Shell. The stack also includes Docker, Shell, .NET.
Dormant — no commits in 2+ years (last push 2023-05-28).
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.