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.
Related
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/)
I'm getting an "Unrecognized Guid format" error when I try to open my project in Visual Studio 2015 on a Windows 10 machine (upgraded from Windows 7).
This did not always occur for me. I originally made VS studio open as administrator (because my project needed it at the time) by following the steps in the anwser here: Can you force Visual Studio to always run as an Administrator in Windows 8?
I then decided I wanted to switch back to not having it open as admin. To try and switch back I again ran the compatibility troubleshooter, this time I selected "try recommended settings". After doing this I am now getting the Guid error every time I open my project and I can no longer run it. I even get it if I open VS as admin like I did before.
I even tried uninstalling Visual Studio and reinstalling it but that did not work either.
I am guessing you used to run Visual Studio as Administrator. This did it for me. The answer is to delete the compatibility entry in the registry.
Type Windows+R on the keyboard to open the Run dialog
Type regedit and press enter
Browse to HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers
Delete the Visual Studio entry
I fixed this on Windows 10 by using the Troubleshoot compatibility tool. It has to do with an extra checkbox being enabled.
Navigate to devenv.exe by right clicking Visual Studio from start, click
properties, and select "Open File Location...".
Right click on devenv.exe and select "Troubleshoot Compatibility".
Click "Troubleshoot Program"
Uncheck "it worked with older versions of windows"
Click "Next"
Click "Test the program"
Confirm everything opens correctly
Click "Next"
Click "Yes, save these settings for this program"
As shown in the image. I am not able to open VS 2013 CE. If I click the link, it just opens a new instance of VS2013 with the same dialog window. So I am not able to click the Sign In link at the upper right corner of the main window. And if I click the Close button, the whole app closes.
It looks like you can't click on the HELP menu to get to the "Register Product" option, as the message box won't let you click on anything else.
My next suggestion is to try to Repair the product.
Go to Control Panel > Programs and Features > Microsoft Visual Studio Community 2013 > Repair (it's one of the options). It will restart your computer, and when you launch VS again, it will display more options on the screen, including Register / Sign in. Sign in using your Microsoft account here. Let me know if this helps!
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).
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?