# Debug Slicer and SlicerRT Together

**URL:** <https://discourse.slicer.org/t/debug-slicer-and-slicerrt-together/26955>\
**Category:** Development\
**Tags:** slicerrt\
**Created:** [December 28, 2022, 5:25am UTC](https://discourse.slicer.org/t/debug-slicer-and-slicerrt-together/26955 "2022-12-28T05:25:31Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [January 4, 2023, 11:17am UTC](https://discourse.slicer.org/t/debug-slicer-and-slicerrt-together/26955/6 "2023-01-04T11:17:30Z")

</div>

Your approach sounds good. This command starts VS for me with the ability to debug Slicer and SlicerRT:  
`..\S5D\Slicer-build\Slicer.exe --VisualStudio --launcher-no-splash --launcher-additional-settings ./SlicerRT_D/inner-build/AdditionalLauncherSettings.ini c:\d\_Extensions\SlicerRT_D\inner-build\SlicerRT.sln`

Then when the solution opens, make sure that you select a project other than `ALL_BUILD` as startup, it can be any of them (qSlicer… or vtkMRML…). Then, in the project settings you need to set the command to be the `SlicerApp-real.exe`, such as `c:\d\S5D\Slicer-build\bin\Debug\SlicerApp-real.exe`. Then when you start the debugger, the breakpoints in Slicer and SlicerRT (and CTK etc) should be hit.

Of course what @pieper suggests with `SlicerWithSlicerRT.exe` should work too, but what I have wrote above is how I have been doing it forever and it still works.

---

_[View the full topic](https://discourse.slicer.org/t/debug-slicer-and-slicerrt-together/26955)._