Visual Studio 2005 context menu launches server explorer: why? - visual-studio-2005

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?

Related

Make Visual Studio 2019 Always Run as Administrator from Start Bar Recent Solutions List

I recently upgraded to Windows 10 and Visual Studio 2019.
Prior to the upgrade, Visual Studio 2017 would always run as Administrator. I did not think much of this, but now that it is gone it is causing me problems.
The primary one is that it will not load my projects that use my local instance of IIS.
I usually launch Visual Studio from my start bar. Right now this goes like this:
Right click on the icon on the start bar and select my solution.
It loads and then I realize that the main project did not load.
Close visual studio, open as admin
Pick my solution and then it loads.
I would really like to only have to do #1 above. Is there someway I can edit the shortcut on the start bar to have it always launch as Administrator?
Turns out that Visual Studio uses different permissions when you click on the list of shortcut options it offers in the start menu. (IE to load a recent solution directly.)
Selecting the Properties->Advanced->"Run as Administrator" did not cause these to run as administrator.
But this did it:
Find devenv.exe (Visual Studio's executable)
Right Click on it and select "Troubleshoot Compatibility".
On the Program Compatibility Troubleshooter window, click on Troubleshoot Program
Check that the program requires additional permissions and click Next
On the next window, click on Test the program… and VS will open as administrator
Click next and then click on Yes, save these settings for this program
Now Visual Studio will ALWAYS run as administrator.
(Taken from: https://ppolyzos.com/2017/08/08/always-run-visual-studio-as-administrator/)

Clicking on a link on Visual Studio pops up a window that won't go away

I have Visual Studio 2012 running on Windows 10. Whenever I click on a link that is somewhere on Visual Studio, a popup window opens up saying "How do you want to open this website?" Can't close it, can't move it, it just gets stuck there. I still can manage other apps.
For example, below is the window I got stuck with when hitting "View All Setting" link on visual studio of an Azure website. How do I stop this without closing everything down through Task Manager.
taskkill /im openwith.exe with admin rights will get rid of this popup from hades.

Greenshot does not work in Visual Studio

Anyone know why you cannot use Greenshot in Visual Studio? I hit the Screen Print button and it does not bring up the cross-hairs to drag my window size. Instead it just takes a plain windows screenshot. I looked for keyboard commands that might override it but didnt see anything at first glance. It works for every other program but not when Visual Studio is the active window.
It's because your visual studio is running in a higher level (permission wise) than your greenshot instance.
for a one time test, close Greenshot, and run it as administrator (right click on the file, run as administrator).
As a more permanent solution, you can just set the compatibility mode for the file to be run in admin mode, and then when it's started on start up it should capture your VS instances as well :).
Edit:
Just in case, you can easily figure out if anything else is wired to a shortcut by doing the following:

How do you prevent Visual Studio 2012 from closing IE when you stop debugging?

When I was using Visual Studio 2010, I could just "Detach All" and the web site would continue to run and the browser wouldn't close. That would enable me to attach a different solution to debug a separately compiled library. Now all that's left is "Stop Debugging" and "Terminate All".
Although the website is still running in the background, I have to open a new browser window and navigate back where I was.
Is there some way to go back to the 2010 functionality?
Detach All is still available in VS 2012. If you don't have it under Debug in Main Menu then you may need to add it manually (right click on toolbar, select Customize.. from context menu).

Visual studio 2005 "Object Test Bench" popup when debugging

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.

Resources