I need to debug an application that is started from a one-click install. (VS 2010, Excel VSTO with Office 7). Based on login credentials supplied to the one-click installer
you could attach to Excel if it was running long enough but seriously I doubt the error is there.
you could attach to running applications/processes and if symbols are available (debug build) you can really debug, but the application has to live long enough for you to select it for attaching.
I think, from what you are saying, that what you need is proper exception and error logging, anything like Log4Net or NLog which stores everything (stack trace, exception details...) at every exception, so you would clearly identify what the real issue is.