Visual Studio 2013: Turn Off the Uppercase Menu

NOTE: This is an older feature. I’ve updated the information for VS2013.

 

This is one change to Visual Studio that I’m not a fan of and I still continue to see a ton of posts on this change so thought I would share here as well. 

 

I always try to give credit where credit is due and I believe the earliest mention of this fix is by Richard Banks in his post 6\1\2012 here:  http://www.richard-banks.org/2012/06/how-to-prevent-visual-studio-2012-all.html 

 

 

 

Mixed Case is Your Friend

Okay so you really, really don’t like the Uppercase menu in VS2012 because you feel like it is shouting at you:

5-16-2012 7-50-41 PM

 

 

You would rather go back to mixed case for your menu:

5-16-2012 7-43-08 PM

 

Not a problem! Below are ways you can fix this feature in VS2013.

 

 

 

Manual Registry Change

WARNING:  Making changes to the registry can cause unexpected results so do any changes at your own risk!

  1. Open the registry editor and go to HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0\General\
    (For Windows 8 Express go to HKEY_CURRENT_USER\Software\Microsoft\VSWinExpress\12.0\General)
    (For Web Express go to HKEY_CURRENT_USER\Software\Microsoft\VSWDExpress\12.0\General)

  2. Create a new DWORD value called SuppressUppercaseConversion set to 1
    image

  3. Restart Visual Studio and you should see the change

NOTE: Watch your spelling if you are typing this manually.

 

 

PowerShell

If you like to “simplify” this a bit you can use PowerShell to run a nice script to make this happen.  However, if you haven’t used PowerShell before this may not be faster for you.

  1. Go to the Start button or (Start Screen in Windows 8) and type powershell then select the Windows PowerShell Entry:
    image

    image

  2. In the PowerShell window copy the script below and paste it in then press Enter:

    Set-ItemProperty -Path HKCU:\Software\Microsoft\VisualStudio\12.0\General -Name `` SuppressUppercaseConversion -Type DWord -Value 1   image

  3. Restart Visual Studio and you are good to go.