So by now this is no longer a new issue and not too difficult to find a fix for. However, when looking for a fix I happened to find several solutions out there and thought I would consolidate some of my findings here.
1) VSCommands for Visual Studio 2012 (http://bit.ly/1dICPOy) – This is an extension created by Squared Infinity. The extension is available directly from inside Visual Studio Online Gallery. Once installed, there are several features available under the VSCommand submenu, including fixing the ALL CAPS menu itemes. The one sticking point for me was their stated license agreement: VSCommand Lite – “Free version for individual developers working on personal or open source projects”; VSCommand Pro – “Paid version with additional features for developers and business customers working on commercial projects.” So much for that option. We have a hard enough time getting money for coffee filters, much less for a cool Visual Studio extension.
2) NuGet gallery package (http://bit.ly/1j2dtm6) – Nuget is a user community open source “Visual Studio extension that makes it easy to add, remove, and update libraries and tools in Visual Studio projects that use the .NET Framework” (nuget DOCS). My primary job function and focus is on SQL Database / BI development, so when I came across this toolset I felt a little out of my element. I’ve heard of NuGet gallery before, but honestly didn’t want to take the time to invest in understanding pros / cons etc…
3) Registry Hack (My choice) – Really! When in doubt, get down and hack it. I want to make sure to give credit where credit is due. After doing a simple online search, I found this fix on Richard Banks blog (http://bit.ly/1aUYVMS). In the end, this is the option I went with. The desktop guys at work tend to get a bit out of shape if you start installing software they don’t control. I get it and want to support their cause, plus if there were ever some kind of security issue with an install, it would suck to be that guy.