Last post May 08, 2012 08:48 AM by bbcompent1
May 07, 2012 11:03 AM|tmyonline|LINK
Guys: The "Start without Debugging" and "Start Debugging" options in my Visual Studio are both dim, never happened like this before. I google searched around but have not found a solution on how to turn these options on. Any ideas ? Thanks.
May 07, 2012 11:13 AM|bbcompent1|LINK
"I have determined the solution to this problem. When I checked my solution properties,
"Multiple Startup Projects" was selected. This was a problem because one of the projects was a database project. Changing the Startup Project to "Single Startup Project" and selecting the proper project allows me to debug the solution."
May 07, 2012 11:20 AM|Bimalvv|LINK
The default is 'basic settings' which does not include the "Start Without debugging" (CTRL + F5) option to start without debugging. Change your settings to Expert to correct this by checking the "Expert Settings" in the "Tools/Settings" Menu.
May 07, 2012 11:21 AM|tmyonline|LINK
Thanks bbcompent1 but I have only one project. Don't know what's going on. So frustrated right now !
May 07, 2012 11:26 AM|tmyonline|LINK
Bimalvv: I found this suggestion on Google but it's really for when the "Start without Debugging" option is not there. In my case, it's there but it's dim (it's being greyed out) and so I cannot click on it.
Anyway, I did look at the suggestion but I could not find "Settings" under Tools, at least in my current configuration. To check on "Expert Settings", I have to have "Settings" first but it's not available under Tools.
May 07, 2012 11:27 AM|bbcompent1|LINK
Ok, Click Tools > Options
Check Show all settings > Check some options in Debugging (is this there?)
Another question, are you using an express version of Visual Studio or one of the paid-for versions?
May 07, 2012 11:37 AM|tmyonline|LINK
I'm using a professional paid version, this is for real work.
I never had this issue before, just today when my machine apparently rebooted itself over the weekend.
I went to Tools > Options > Debugging > General, there is no such thing called "show all settings".
There are so many categories under Tools > Options, which one should I look at ?
May 07, 2012 11:42 AM|Bimalvv|LINK
Did you reset the settings by selecting Reset all settings option in Tools->Settings->Import and Export Settings?
May 07, 2012 11:42 AM|bbcompent1|LINK
Ah ok, you do have it checked already (Its a checkbox at the bottom of the window). So this happened over the weekend? I would suggest using Windows System Restore utility to undo any changes made over the weekend. That would be the easiest fix.
Start > Accessories > System > System Restore
May 07, 2012 11:53 AM|tmyonline|LINK
I did as you said but the options Start without Debugging and Start Debugging are still dim.
May 07, 2012 11:57 AM|tmyonline|LINK
I did as you said, I went to Start > All Programs > Accessories > System Tools > System Restore. Initially, this option was turned off. I just turned it on. It then asked me to select a bold date on the calendar for the Restore Point but I cannot click
on Friday, May 4, for the Restore Point.
May 07, 2012 11:58 AM|bbcompent1|LINK
Check out this thread as it sounds similar to what you're experiencing:
May 07, 2012 01:58 PM|tmyonline|LINK
Unfortunately, this does not solve the problem. Is there any reason as to why the "Start without Debugging" option goes dim and how to turn it back on ? Thanks.
May 07, 2012 03:45 PM|tmyonline|LINK
Just an update, I was able to enable the Start without Debugging and Start Debugging options, they are no longer dim.
I decided to create a "New Project from Existing Code" and attach my project to it.
But now, I have a different problem, my Visual Studio does not seem recognize my "using statements" above every class. For example,
using System; // no error here
using System.Web.UI; // a red underline appears under "UI"
using System.Drawing; // a red underline appears under "Drawing"
Any idea ? Thanks.
May 08, 2012 08:48 AM|bbcompent1|LINK
I would add references to those namespaces in your project. Its possible something got pooched in the web.config assemblies section.