Visual Studio 11 and Windows 8

The trade press is beginning to talk about Visual Studio 11 quite a bit more often now, even though the release of the initial beta won’t even happen today (coincident with the consumer release of Windows 8). The word on the streets is that you won’t see anything too exciting or unexpected in Visual Studio 11. Yes, Microsoft is making the usual laundry list of changes, but there isn’t anything that you wouldn’t expect them to add. Here’s a quick overview of the changes that I’ve been able to glean from the various articles I’ve read:


  • HTML5 and JavaScript support
  • Touch application support
  • Agile application development
  • Cloud application development
  • .NET Framework 4.5 support
  • Metro interface designers
  • Devops integration (a tool designed to make it easier for administrators and developers to communicate)
  • IntelliTrace updates that make it possible to trace activity in operational applications
  • Asynchronous programming updates
  • Parallel program development
  • Improved SharePoint support

In other words, Visual Studio 11 is targeting Windows 8 and Windows Azure development. Along with these changes, there are rumors that Microsoft will simplify the IDE to make it easier to use. I just hope that they don’t bury functionality in places where you can’t find it. The Ribbon interface that Microsoft is so fond of adding to other applications does just that—making them a nightmare for power users to use, while simultaneously reducing the learning curve for the novice (the bad and the good that comes with any change).

There isn’t any mention of one of my pet peeves with Visual Studio 10, it’s voracious appetite for system resources and an unflinching desire to freeze the system. The current version of Visual Studio tends to require me to reboot my system at least once during any programming session.

Also missing from the laundry list is any mention of Silverlight, which makes me wonder whether Microsoft is putting this technology out to pasture. In addition, there was nary a mention anywhere of updated Windows Phone support. You’d think that Microsoft would be providing some updated support for Windows Phone development considering that many developers will need to support the mobile device. More and more users are augmenting their desktop systems (or replacing them entirely) with mobile devices, so Microsoft had better get on the ball.

Everything I’m reading focuses on Microsoft’s two main languages C# and Visual Basic. For example, I haven’t seen anything about F#, which appears in the current product. Of course, IronPython was orphaned quite some time ago, but the IronPython community remains alive and well (see my IronPython 2.7.1 Update post for details). This lack of information makes me wonder about the future of Microsoft’s other languages (including C++).

Of course, the updates in Visual Studio 11 and the .NET Framework 4.5 will affect applications of all sorts. During the upcoming months I’ll try to test all of the application examples in my books to determine whether there are any issues you need to know about. In the meantime, please continue to use the supported versions of Visual Studio when working through the examples in my books to ensure you have the best learning experience possible. Contact me with any concerns or observations you have about Visual Studio 11 at