If you mean debug a web application that is running in IIS instead of the development server, then "Attach to process" is the way to go. This means selecting in the debug menu "Attach to process" instead of "Start Debugging". You will see a dialog a bit like the task manager and will need to select the process to attach to. For IIS this will be w3wp.exe. There will most likely be more than one instance of w3wp.exe running - so selecting the right one will be the real trick. Set a debug point in the source - if you're connected to the right w3wp instance the debug point will look as normal rather than having the warning sign (and looking flat and white). I was doing this today and used this as a reference.