Adopting Debug Adapter Protocol in Eclipse IDE: netcoredbg (.NET debugger) case study
summary
Shows that the Debug Adapter Protocol can be wired into Eclipse with modest effort: uses LSP4J/LSP4E to implement the JSON message client/server and to expose IDE views, and integrates the open source netcoredbg as the backend. The outcome is a working C#/.NET Core debug flow—launch JSON generation, breakpoints, stack/variables and simple memory views—built fast inside aCute with only UX wiring and launch-config plumbing. Claims reduced coupling and multi-language reuse; integration cost is mostly launch/config handling, not core protocol work.
AI-written summary · about
chapters (10)
- 0:00Adopting DAP in Eclipse
- 3:50What is DAP
- 8:27DAP benefits and use cases
- 13:17DAP in Eclipse ecosystem
- 18:54netcoredbg case study
- 23:30Configuring and using DAP
- 27:23DAP flexibility
- 32:05Experience and best practices
- 36:10DAP implementations
- 40:14Conclusion
related talks
57mExtend the new WinDbg to build your own dream debugging tool
56mHidden Difficulties of Debugger Implementation for .NET WASM Apps
59mBuilding your own debugging toolbox with ClrMD
51mHidden Difficulties Implementing a Debugger for .NET WASM Apps
03mInterview Speaker
01h 16mBuilding Mobile and Desktop Apps with VS and .NET MAUI
53m.NET Debugging tricks you wish you knew
44m.NET Aspire development on any OS with the Visual Studio family