I can't seem to get execution to stop at any breakpoints. I've verified debug is enabled in web.config and project properties.
When I was previously working on this project on another machine, (a long time ago)breakpoints worked. Now, I'm working on the project on a different machine (running Windows Vista) and I can't get breakpoints to work. I've tried setting breakpoints in different methods (C#) in different aspx pages, and nothing is stopping. I'm using inline pages, not codebehind.
I'm completely stumped. The project I'm working with is based on the Club Starter Kit, and I've tried setting breakpoints on stuff like Page_Load events that was part of the kit, and they don't even work.
My environment is Web Developer Express, running on WIndows Vista Ultimate RC2.
Any thoughts on what I need to do?
If there is any information I can provide to help troubleshoot, please let me know.
Thanks,
Gary
I eventually found an answer to help me in another post that I didn't find before posting my question.
When launching Web Dev Express on Vista, if I right-click the shortcut and choose "Run as Administrator", debugging works for me. I didn't realize I would need to run under elevated privileges to debug and have breakpoints work.
Another post I found mentioned adding "LocalHost" to trusted sites, but that didn't make sense to me, as I interpret LocalHost being use for SQL stuff.
Thanks,
Gary
Is there anyway in Vista to stop vs2005 from prompting me every time I run it now to allow access as admin?
Yes, but it will also stop the prompting for other apps when launched by an admin, which you may or may not find desirable.
Open Vista's Help system and search for UAC. This should return topics for Vista's User Account Control (UAC) system, which is what is behind those dialogs asking you to allow a program to launch, even when logged in as an admin. The topic of interest for you is "How do I change the behavior of the User Account Control message?" Walk through the instructions for changing the User Account Control Message for administrators in Admin Approval Mode. You will want to change to "Eleveate without prompting". I just tried this on my system and it works. Keep in mind that this change is to the system so it impacts all apps running as admin. I'm no security expert, so I can't say if this change makes your system more vulnerable or not. MSFT wants to ship more secure systems, so they tighten things down by default and have been moving that way for awhile. It's up to the user to "loosen up" the system so it's their choice to make it more vulnerable or not.
One other thing to note is that if you want to run an app as an admin, there is a "Privilege Level" property on the shortcut used to launch the app you may want to look at. Right Click the app's shortcut and choose properties, go to the Compatibility tab. At the bottom in the Privilege Level section, there is a "Run this program as an administrator" checkbox. I have this checked on my VS shortcut so VS always as an admin so breakpoints work right. It's been awhile since I installed VS, so don't remember if this was marked by default or not. Anyway, if that is marked, and you make the changes for the behavior of the User Account Control message, VS will launch without prompting you to allow it to launch.
hope that helps,
Gary
User Account Control (UAC) is a new security component Windows Vista.UAC enables users to perform common tasks as non-administrators, calledstandard users in Windows Vista, and as administrators without havingto switch users, log off, or use Run As.
By separating user and administrator functions whileenabling productivity,It helps eliminate the ability for malware to invoke administrator privileges without a user's knowledge. So is not recommended to turn off User Account Control in Vista.
The way "Run this program as an administrator" provided by glura is best idea i think if you know your app well.
0 comments:
Post a Comment