http://mschnlnine.vo.llnwd.net/d1/Dev/App_Themes/C9/images/feedimage.pnghttp://channel9.msdn.com/forums/Coffeehouse/230417-Understanding-the-basics-UAC-and-VS2005/Understanding the basics (UAC and VS2005)http://channel9.msdn.com/forums/Coffeehouse/230417-Understanding-the-basics-UAC-and-VS2005/en-usSun, 17 Sep 2006 21:13:27 GMTSun, 17 Sep 2006 21:13:27 GMTEvNet (EvNet, Version=1.0.3608.3122, Culture=neutral, PublicKeyToken=null)<BLOCKQUOTE><div>Sven Groot wrote:</div><div><BR>...<BR><BR>As for the issue at hand, I don't know. I haven't tried IIS, but I have no trouble debugging VS2005's&nbsp;built-in&nbsp;web server.<BR><BR>The debugger detaching immediately when debugging with IE is a known problem, it is caused by IE's Protected Mode. The solution is to either first start IE, then attach manually, or to add the site you're testing to the Trusted Sites, which disables protected mode for that site.</div></BLOCKQUOTE><BR><BR>Good stuff, the protected mode settings solved the issue with the development server.<BR><BR><BR>No influence on IIS though.<BR>The application pool is running with my credentials, and the task manager shows that it is.<BR><BR>I also tried to attach the debugger, but the Available Processes dialog in VS does not display any user name for the w3wp process, and does not allow me to attach.http://channel9.msdn.com/forums/Coffeehouse/230417-Understanding-the-basics-UAC-and-VS2005/?CommentID=230451Sun, 17 Sep 2006 21:13:27 GMThttp://channel9.msdn.com/forums/Coffeehouse/230417-Understanding-the-basics-UAC-and-VS2005/?CommentID=2304510http://channel9.msdn.com/230451/WebViewBug.aspx?EVT=0Sven Groot wrote:...As for the issue at hand, I don't know. I haven't tried IIS, but I have no trouble debugging VS2005's&nbsp;built-in&nbsp;web server.The debugger detaching immediately when debugging with IE is a known problem, it is caused by IE's Protected Mode. The solution is to either first&#8230;borosen0http://channel9.msdn.com/230451/Trackback.aspx<BLOCKQUOTE><div>borosen wrote:</div><div>With this UAC stuff, I figure it is ok to run with admin account, so I log off and log on again with an admin account, ready to do some more.<BR><BR>Guess what! <BR>Not able to start debugging on the web server. Again?!<BR>I just tried it didn't I? What is going on!?!</div></BLOCKQUOTE><BR>When UAC is enabled and you are logged in as&nbsp;an admin, you still don't have admin rights. That's the idea behind UAC. As an admin, you can still right-click and choose "Run as Administrator", then you are asked to elevate and the app will have full admin rights.<BR><BR>As for the issue at hand, I don't know. I haven't tried IIS, but I have no trouble debugging VS2005's&nbsp;built-in&nbsp;web server.<BR><BR>The debugger detaching immediately when debugging with IE is a known problem, it is caused by IE's Protected Mode. The solution is to either first start IE, then attach manually, or to add the site you're testing to the Trusted Sites, which disables protected mode for that site.http://channel9.msdn.com/forums/Coffeehouse/230417-Understanding-the-basics-UAC-and-VS2005/?CommentID=230444Sun, 17 Sep 2006 20:49:13 GMThttp://channel9.msdn.com/forums/Coffeehouse/230417-Understanding-the-basics-UAC-and-VS2005/?CommentID=2304440http://channel9.msdn.com/230444/WebViewBug.aspx?EVT=0borosen wrote:With this UAC stuff, I figure it is ok to run with admin account, so I log off and log on again with an admin account, ready to do some more.Guess what! Not able to start debugging on the web server. Again?!I just tried it didn't I? What is going on!?!When UAC is enabled and you are&#8230;Sven Groot0http://channel9.msdn.com/230444/Trackback.aspx