...
Make the following settings:
Debugger to Launch | Remote Windows Debugger |
Remote Command | C:\Windows\System32\ |
inetsrv\w3wp.exe | |
Remote Command Arguments | -debug |
Working Directory | c:\opt\shibboleth-sp\.... |
Remote Server name | whatever.example.org:4020 (gotta have the port) |
Connection | default (auto) or "Native Only" |
Deployment Directory | C:\Windows\System32\intersrv\ (for ii7_shib). Probably C:\opt\shibboleth-sp\lib64\shibboleth\debug for isapi-shib |
Set an appropriate break point. When you try to run the project for the first time there will be a login dialogue (login with an admin user) then the Remote Debugger tool will show you to be logged in. Finally a command window will pop up as IIS starts.
...
These are the settings I use
Debugger to Launch | Remote Windows Debugger |
Remote Command | C:\opt\shibboleth-sp\sbin64\debug\shibd.exe |
Remote Command Arguments | -console |
Remote Server name | whatever.example.org:4020 (gotta have the port) |
Connection | default (auto) or "Native Only" |
Deployment Directory | C:\opt\shibboleth-sp\sbin64\debug |