Thanks to AMD’s president and CEO Lisa Su on their latest earnings call last week, she said that the release date for Windows 10 is sometime in late July. Having worked at Microsoft, this isn’t really big news since that is when they usually do it unless it slips to August for whatever reason. There is always a time gap between when they release RTM and when it’s available internally, to MSDN subscribers, and to the general public. The part that hasn’t been covered is if that’s the RTM release date, where we normally wouldn’t see the bits for a few weeks afterwards, or if RTM is actually earlier than that, and this is one of the other availability dates. I’m leaning towards the earlier release date when they call it good for shipping and producing the official binaries.

Windows and Visual Studio have usually always gone hand-in-hand together for release and availability as well given that one is the official tooling to develop on the other and they need some sort of lock-step development plan. It may not be the same days, could be as much as a couple of weeks apart given Windows is larger code-base. Either way, we’re getting close to getting the newest versions of both Windows and Visual Studio soon.Continue reading

I’m having a hard time trying to understand how Microsoft open sourcing .NET is going to help them, at least financially. I get that developers want to have the option of running on Linux, and that by doing this, they win the development community. Microsoft has a horrible history of not always choosing right over profitable.

With the status quo prior to this last week, the use of .NET on non-Windows machines meant you were a year or so behind the curve by using Mono. At least depending on what you wanted to implement – some of the asynchronous parts of the MVC framework is still out of reach, and both WPF and WCF were left entirely unimplemented.Continue reading

If you happen to be giving Visual Studio 2012 RC a run around the block and noticed all of the menus are in CAPS, you can drop this in a Setting.reg file and import it…


If you decided that you want to go back, change the contents of the file to the following and import it again…


Update (10/13/2014):

These same instructions can be applied to Visual Studio 2013 as well by substituting the ‘11.0’ value for ‘12.0’. For those of you using Visual Studio Express 2013 for Web, the same instructions while substituting the ‘VisualStudio’ value for ‘WDExpress’ will work.

With whatever version you are using, if you don’t want to open the Registry Editor, you can also enable it using PowerShell and the appropriate registry string like so…

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