As a daily user of Visual Studio from its inception, and of Visual C++ and Visual InterDev before that, I have been following the evolution of Microsoft's development environment quite closely. In the Visual Studio 2010 IDE, Microsoft has taken several large steps away from its legacy code. That was a gutsy and potentially risky move on the part of the Visual Studio team, but one that worked out well and will lay the foundation for future product growth.
Visual Studio 2010 is a major upgrade in functionality and capability from its predecessor. It includes some major rewriting of core features, as well as many new features. Developers, architects, and testers will all find areas where the new version makes their jobs easier. Despite the higher pricing for this version, most serious Microsoft-oriented shops will upgrade to Visual Studio 2010 and never look back.
Raising the bar for IDEs
The most obvious large step is revamping the core editing and designer views to use the Windows Presentation Foundation (WPF). I covered this and the related improvements in the UI and debugger in my review of Visual Studio 2010 Beta 1. Initially there were some performance penalties associated with this, but now almost everything I do in the Visual Studio 2010 IDE happens faster than it would in Visual Studio 2008, even columnar text selection. I particularly like the navigation improvements in the code editor. Both the "Navigate to" and "Call Hierarchy" features have proven invaluable to me recently as I learned a large C++ code base.
Another obvious large step is to revamp IntelliSense and start to support Test-Driven Development (TDD). As I discussed in my reviews of Visual Studio 2010 Beta 1 and Visual Studio 2010 Beta 2, IntelliSense has been redesigned, the easily corrupted IntelliSense .NCB file has been eliminated, and the whole system has become more sensible about offering to do what you might actually want instead of cavalierly completing your typing with irrelevancies. At this point, Visual Studio 2010 is usable for test-driven development (TDD), although I wouldn't yet call it a real TDD-oriented system. For me, that would require another view of a project that emphasized a Red, Green, Refactor development cycle.
|Test Center Scorecard|
|Microsoft Visual Studio 2010||10||9||9||9||9|
You may still be better off sticking with Win7 or Win8.1, given the wide range of ongoing Win10...
Now that we're down to the wire, many upgraders report that the installer hangs. If this happens to...
Based on a technique created by a German blogger, here's how to stop wasting hours checking for Windows...
Everyone benefits from Network Time Protocol, but the project struggles to pay its sole maintainer or...
We reviewed a lot of gadgets and services in 2016, and here are our top 12 recommendations for tech...
The kit helps developers build apps that boot as OSes and are less dependent on hardware
Were it not for an alert customer, attackers could have compromised every RHEL instance on Microsoft...