Remote debugging ASP.NET applications using Visual Studio 2008

re: Remote debugging ASP.NET applications using Visual Studio 2008

brian-murphy-booth — Fri, 02 Jan 2009 14:26:44 GMT

Oliver,

Imagine if you created a feature in your application that was used by 1% of your users, but created 25% of your support calls. Imagine that there was nothing you could do to make your feature any easier to use in order to try to illiminate those support calls. You might be tempted to remove that feature. Microsoft occassionally runs into that sort of situation and I am *guessing* that this is one of those situations. Remote debugging has never been a solid solution for various reasons that I won't go into [so that you can't prove me wrong]. As a support engineer I am actually pretty happy that this feature is gone! To me at least, it makes sense that this feature has been removed.

re: Remote debugging ASP.NET applications using Visual Studio 2008

olivierH — Fri, 07 Nov 2008 21:43:10 GMT

Have to try this as soon as I get back to work.

I've spent hours figuring how to debug a remote asp.net website from a vista workstation editing with VS2008. Without luck. this could be my last change

Note: I run Remote Debugger on Windows Server 2008 (where IIS7 resides) as a service, but can't see no "debugger" group or user?

Furthermore, event if this solution works (which would be at least some solution), there must be a better way ??!!?? People at MS certainly figured out how it can/should be done ... since it seems quite a "natural" feature to remotely debug, at least on an isolated private local network ....

re: Remote debugging ASP.NET applications using Visual Studio 2008

Shailesh — Thu, 31 Jul 2008 04:45:22 GMT

Your script helped a lot with little changes. :)

Thanks.