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/)
Previously if I set a breakpoint in a cshtml file I could hover over a variable and Visual Studio would tell me the value.
Now when I hover a variable in cshtml, it just tells me the type... And I have to individually Shift+F9 (quickwatch) on every variable I want to see the value of.
How do I get back the hover showing the value?
Is the a change in a recent Visual Studio update? I'm using 15.7.3
I've already tried resetting to default settings, and still get the issue
Turns out it was a bug in Visual Studio Community
Fixed in Visual Studio Community 15.7.5
See first item in release notes:
https://learn.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes#top-issues-fixed-in-1575
I saw in a video talk by Bart de Smet where he was running Windbg commands by typing them into the Immediate Window in Visual Studio when running the project in debug mode inside the Visual Studio debugger.
So, I wanted to try that myself. So here's what I did:
I went to the Project Properties dialog and then selected the Debug tab, then checked the Enable native code debugging in the Enable Debuggers section.
I set a breakpoint on one of the lines and then launched the project with debugging by hitting F5. When the breakpoint was hit, I opened the Immediate Window and typed the .load command to load sos.dll.
But the message I got as a result read:
.load "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\sos.dll"
error CS1525: Invalid expression term '.'
Is there something else I need to do?
I am using Visual Studio 2015 Community edition.
Run your application without debugging
Choose Debug/attach to process ...
Choose "Windows User Mode Debugger" as transport
Click "Refresh"
Choose your application
Click "Attach"
Open the "Immediate Window", which will labelled be "Debugger Immediate Window"
Enter WinDbg commands
In Visual Studio 2013, Microsoft again presents the menu in UPPERCASE as the default.
Can these be modified to be Sentence Case?
Yes - in the new Visual Studio 2013 (as in VS 2012), MS reinforced their design decision to make ALL CAPS MENU ITEMS the default. The methods for reverting the menu style are almost the same methods used for Visual Studio 2012, which has been discussed before.
Update (after Visual Studio 2013 Update 4)
As of Visual Studio 2013 Update 4 you can go into Tools > Options > Environment
and uncheck Turn off upper case in the menu bar
Before Visual Studio 2013 Update 4:
You need to create a specific registry key if you want "old-style" menus back.
First Variant: Since Package Manager Console is Powershell, select menu options TOOLS / Library Package Manager / Package Manager Console and enter and run
Set-ItemProperty -Path HKCU:\Software\Microsoft\VisualStudio\12.0\General -Name SuppressUppercaseConversion -Type DWord -Value 1
(as a single line).
Second Variant: Open up a Command Prompt (win+r, cmd, enter) and enter and run
REG ADD HKCU\Software\Microsoft\VisualStudio\12.0\General /v SuppressUppercaseConversion /t REG_DWORD /d 1
(as a single line).
Third Variant:
Change registry values by hand, open regedit and navigate to
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\General
then, create (right click):
DWORD value
with the content of
SuppressUppercaseConversion
and set it to
1
Close regedit.exe and you're done.
Fourth Variant: At least one VS Extension (VSCommands for Visual Studio 2013) has been published that enables you (among other things) to switch menu style via config menu from within VS 2013.
You may also set it to all-lower-case items (which is, imho, nice):
switch to Sentence Case (subtly different from what you get with SuppressUppercaseConversion: the SQL menu gets renamed to Sql)
or hide it completely (and have it appear on ALT key press or mouse over)
After years Microsoft has changed their mind on this feature. As of Visual Studio 2013 Update 3 RC, an option has been added in Tools -> Options to change to Mixed Case for Menu titles. Obviously this is not for VS 2012 but going forward this option will be there.
Here is the notification from Brian Harry of Microsoft....
Mixed Case Menus – I know I’m going to get some feedback on this one :) This is a long standing request by a vocal portion of the VS user base since VS 2012 to change the “ALL CAPS” menus. In VS 2013 Update 3, we have added a Tools –> Options setting to control whether you see ALL CAPS or Mixed Case. The default is still ALL CAPS but, if you change it, it will persist across upgrades and will roam across your IDE instances using the VS Online roaming settings feature (if you log into VS so it knows who you are).
http://blogs.msdn.com/b/bharry/archive/2014/07/02/vs-tfs-2013-3-update-3-rc.aspx
I have been using the following reg files to enable/disable the lowercasing in Visual Studio 2013:
http://erwinmayer.com/dl/VS2013_ALLCAPS_Toggle.zip
Just double click on VS2013_ALLCAPS_Disable.reg inside the archive to disable all caps menu titles, and VS2013_ALLCAPS_Enable.reg to re-enable them.
You can easily edit the reg files before with a text editor to see what they contain.
If you're using the "Visual Studio Express 2013 for Windows Desktop" version the registry key should be added in:
HKEY_CURRENT_USER\Software\Microsoft\WDExpress\12.0\General
So simple! You can go to Tools -> Options -> Environment -> General tab and check the Turn off uppercase checkbox from the right side and click ok. Visual studio 2013 will automatically turn off uppercasing of the menubar.
VS 2013:
Tools→Extensions and Updates→Online,
Type "VSCommands" in search textbox,
Click Download
Tools→Options→VSCommands→General,
Click Open-Configuration button
IDEEnhancements→Main Menu→Change Main Menu Letter Case,
click Sentence-Case
I have set up my system to automatically attach the visual studio debugger when a certain application is launched using these instructions:
http://msdn.microsoft.com/en-us/library/a329t4ed%28printer%29.aspx
The problem is that I get a dialog box each time that requires me to confirm that I do indeed want to attach the debugger. The dialog also prompts me to specify which visual studio debugger I want to attach (I have VS2003, VS2005 and VS2008 installed on the system). I've selected "New instance of Visual Studio 2008" and checked the "Set the currently selected debugger as default."-box but the dialog keeps popping up.
Thanks
Andreas Brinck
There is a registry entry that determines how the debugger is started. Under
HKLM\Software\Microsoft\Windows NT\CurrentVersion\AeDebug
create a DWORD value named "Auto" with a value of 1, so no confirmation window displays