tag:blogger.com,1999:blog-3930375442497799514.post-31400449840527654142008-05-06T09:07:00.002-07:002008-05-06T09:18:20.832-07:002008-05-06T09:18:20.832-07:00I've got an asp.net app running on a server, VS2008 running on my desktop, and I can attach the VS debugger to the w3wp.exe processes on the server. When you hit the website in the browser, the breakpoints in your local code just work. Here's how I set it up... <ol><li>I copied msvsmon.exe and msvsmon.exe.config to a folder on the server On my box, they were at "c:\program files\microsoft visual studio 9.0\common7\ide\remote debugger\x86" (There are x64 and ia64 folders as well) </li><li>I launched msvsmon.exe on the server This creates a monitor called [myLoginName]@servername </li><li>In the Tools-Permissions window, I added my regular login account as having debug rights (I have to log into the server as an admin account) </li><li>On my dev box, in Visual Studio, I chose Debug-Attach to process </li><li>I typed in [myAdminLoginName]@servername to match the name of the monitor </li><li>I clicked the Refresh button, and voila! -- a list of processes</li></ol>There's one downside. When I do step 3, then close msvsmon.exe, it doesn't remember that I added my account the permissions, so each time I run it I have to re-add the permission. Luckily remote debugging isn't something we do on a daily basis.Tom Puleohttp://www.blogger.com/profile/10697521511530638404noreply@blogger.com2