When debugging a project in Visual Studio 2005, I have recently noticed a brief appearance of the "Object Test Bench" window. This window appears and then disappears after less than a second and does not look like the normal "Object Test Bench" window one sees when not debugging, as it looks like this:
alt text http://www.beok.co.il/images/ObjectTestBench.jpg
I would like to stop this window appearing and have tried the following:
Closing all Object Bench Test windows when not debugging
Resetting Visual Studio to default settings (devenv /ResetSettings)
Any other ideas?
Migrated? Hmm no code in this question. Anyway is the Object Test Bench perhaps open, but docked, so it pops up when the IDE state changes?
More info on the OTB on MSDN here :)
Edit: Here is what my VS 2005 OTB looks like.
alt text http://i.imagehost.org/0989/otb.gif
I also have the same problem. I once had JetBrain's Resharper 4.5 installed. I uninstalled it after my trial expired, and I think that's when I noticed the Object Test Bench popping up when I debug.
Did either/both of you have Resharper or any other Visual Studio add-on installed/uninstalled before this problem?
Related link on stackoverflow
I had what may be a similar problem: not just the Oject Test Bench, but also Breakpoint, Call Stack, and other windows popped up all over whenever I ran in Debug mode. It started during a project with a single page containing several (probably incompatible) jQuery scripts.
What worked for me was to click on Window -> "Auto Hide All", then again on Window -> "Reset Window Layout". That seemed to resolve it.
Go to on Window -> "Auto Hide All", after go on Window -> "Reset Window Layout". That will resolve the problem it.
Related
I use. VS 2013 Express
When debugging, I need to stop automatically on exceptions.
try to follow this.
http://msdn.microsoft.com/en-us/library/d14azbfh.aspx#AddExceptionsCommand
It says I need to add Exceptions command to the Debug menu
On the Tools menu, click Customize.
The Customize dialog box appears.
Click the Commands tab and, in the Menu bar list, click Debug.
Click Add Command.
In Categories in the Add Command dialog box, click Debug.
In Commands, click Exceptions and then click OK.
But in stage 6, in Commands there is no Exeptions
Also I tried to remove Enable just my code, And it didn't work.
Just a FYI ---
Im am using VS Express 2010 (VB) and didn't see the debug exceptions.
Based on the screen shot above I just pushed CRLT-ALT-E and it opened.. (!)
Its a bit unclear to me, if VB 2010 Express has this option or not, or how to unhide it, but the key click combo opened it.
I was then able to turn off the option I needed
In my case the "PInvokeStackImbalance"
enter image description here
Another user has reported the missing 'exceptions' on the 'debug' menu to Microsoft and actually got an acknowlegement from Microsoft (though not from the product team and not confirmation that it is a bug).
https://connect.microsoft.com/VisualStudio/feedback/details/882780/exceptions-comman-missing-in-vs-2013-express-for-web
For what it's worth, you can add your vote to this report at that site; I'm experiencing this problem and I have done so too.
Here's a potential work-around: the 'exceptions' is present in the Visual Studio Express for Desktop. And you can install that edition side-by-side with Web edition. If you can figure out a way to invoke your project executable from the debugger in the Desktop edition, you'd have control over exceptions there.
The exceptions menu isn't shown in Visual Studio Web Developer Express. It is only shown in Visual C# Express.
You can however break on all exceptions. You can try to turn off "Just My Code" debugging, which will catch exceptions thrown in CLR code and linked libraries.
To do this, open Tools -> Options -> Debugging -> General, and uncheck "Just My Code" (or Enable Just My Code).
if it doesn't work try
Debug -> Exceptions -> Common Language Runtime Exceptions - check "when thrown"
if you don't see exceptions try to change your settings following this guide
Refer here for documentation.
update
if it still not working try this
Tools menu >> Import and Export Settings >> Reset all settings. Then choose C# Development Environment.
Many of the customization and integration features for Visual Studio's IDE are not available in the free Express editions, but you should be able to get to the Exceptions menu easily enough without using them.
Press F5 to start debugging, then select Debug / Exceptions... Turn on the check box for "C++ Exceptions" "Thrown". Hit "OK"
Any idea why Visual Studio peek definition will not work for any project or solution? I have a web, WP and a couple other ones. I can click on a class or method or property and click alt+F12 or right click and select peek definition. The peek window pops up with a progress bar like it is working but just hangs there. Nothing ever shows up in the peek window. Half the time I get this and half the time VS just crashes on me when I try and launch it. I have done a VS repair but that changed nothing.
So I uninstalled a couple dev prod tools and then did another repair and this time it fixed the issue. Peek pops up right away. So something was getting in the way.
I'm running Visual Studio 2010 (10.0.40219.1 SP1Rel) with ReSharper 5.1 (5.1.3000.12). Recently, it seems as though ReSharper has completely lost the ability to navigate to a type.
Here are some actions I can take in the UI that now do nothing:
Right-click on type name in code
editor and select "Go To
Declaration"
Right-click on type name in code
editor and select "Go To
Implementation"
R# "Go to type" (Ctrl-T)
In the R# "Find Results" window, double-clicking a type
Here are some actions that still work:
Double-clicking an item in Solution Explorer
Opening a file from VS Command Window
I've completely uninstalled Visual Studio, then reinstalled it with SP1, and ReSharper 5.1, and I still have the same problem.
I'm assuming there's some kind of configuration open that I've done that is disabling the ability to navigate to a type with ReSharper, I just can't figure out what it is.
Any advice would be much appreciated.
I just experienced this problem. None of the previous suggestions worked for me unfortunately, but I managed to resolve it:
Go to Resharper -> Options
Under Keyboard Shortcuts, temporarily switch to a different scheme than the one selected
Press 'Apply Scheme' button then press Save
hen repeat, but this time select the scheme you actually want and press 'Apply Scheme'
Hopefully that fixes it!
I am using VS 2010 SP1 (same as you)
Delete the Resharper temp files in the same location as your solution file. The folder name will be something like _ReSharper.SomeSolution
Failing that, try one of the R# nightly builds here altho it should work with your current config.
Can someone tell me why my Ctrl+F5 disappeared in Visual Studio 2008? Its not even in the menu. In the Debug menu, All I have is Windows, Start Debugging, Step Into, Step Over, Exceptions, and Toggle Breakpoints.
I'm using the professional edition of Visual Studio 2008 and for some reason, this morning, it just vanished.
You can re-add it: Tools -> Customize... -> Commands tab -> Select Debug -> Drag the "Start Without Debugging" command to the Debug menu and place it where you want it to be.
As for why it happened, hard to tell.
Was it the button there before becuase I just checked on mine and saw that there was no button with Ctrl+F5, but when you do the command, it works fine.
Right click on the menu bar and click Customize... from there you can add in any options that are missing.
Could this happen if the current "Startup Project" - the one in bold in the Solution Explorer - is not an executable?
(I don't have access to VS to check)
For some reason, a variety of actions in Visual Studio 2005, actions that have nothing to do with SQL Server, are opening the "Connect to SQL Server" dialog. And it takes four (4) clicks on the CANCEL button to kill the dialog.
For example, if I right click on a class method in the Editor, hoping to find the Go To Definition option, the dialog opens.
Or if I run a project in Debug mode, and then close the app, the dialog opens.
I have to close VS and re-open it to get this to stop. But after a while, this behavior returns. What is causing it has eluded me.
Is this Microsoft's way to get me to upgrade to VS2008? OK, he's had VS2005 for too long. Time for him to upgrade. Invoke DriveCustomerMad.
Next time you see the dialog box, open a second copy of VS2005, attach its debugger to the first one, pause the process, and look at the call stack.
Do you have any addons installed?