Parallel programming is a theme in Visual Studio 2010. C++ gets the Parallel Pattern Library, and .NET Framework 4.0 gets the Task Parallel Library and Parallel Language Integrated Query (LINQ). This is smart stuff, wrapping complexities such as ensuring that the number of threads used matches the number of available processors, and providing simple abstractions like parallel for loops.
Unfortunately all the pitfalls of concurrent programming still exist, so expect an increase in subtle and unpredictable bugs as this becomes popular. Visual Studio supports it with a new Tasks debugging window and easier thread debugging.
Merge visualization tool shows branches in red where bugs remain
What about Team System? Guckenheimer outlined three major areas of change. The first is in application quality. Gated check-in means you cannot check-in code that does not build. An elaborate new debugging system lets you deploy an application in a test environment with tools that capture bugs as they happen.
"You can file a bug, and with the bug come the exact steps that the tester did, indexed into a video, with screenshots, and with traces of the actual code execution," Guckenheimer said. "The developer can open the bug, click into the trace and open a session that looks like a debugging session but without ever loading the code."
The next area of change is in what Guckenheimer called "business alignment" - new dashboards and deeper hooks with Excel, Project and Sharepoint, for requirements analysis and work breakdown. The third change comes in work on performance. "We think we scale up to pretty much any size team, any number of thousands," he said. There is also a new client, code-named Camano and written in WPF, aimed solely at testers.
A weakness is that Microsoft still largely leaves integration with other platforms to third parties. For example, Eclipse users need Teamprise. On the modeling front, there is a new Architecture Explorer which creates visualizations from existing code. There will also be support for UML diagrams including Class, Use Case, Sequence, Activity, and Component.
The current preview of Visual Studio 2010 is slow and not entirely stable, a fact not helped by running only in a virtual machine, though it does contain a useful set of walkthroughs for Team System.
There is more to come, but from what I've seen so far this is shaping up to be a major release for Windows developers. ®
@ DLL Hell
Putting version numbers in the filenames is the easy part. Just rebuilt the CRT from source (which is provided with VS2005 onwards) and call it whatever the hell you like (Except MSVCRT). There are even mak files provided to make the rebuild even easier.
On a side note, this allows you to turn any optimisations off that you may not want - e.g. Frame Pointer Ommission.
@Tony Hoyle you don't have to install to the app directory, you can install to System32 which I believe will be the preferred approach - as I understand it, it is "like VC 6". Yes, there is a risk of DLL hell.
Great... more slow buggy features...
How about a new feature called "usability" where it can run OK on a machine with 2GB of RAM, and average hardware. I've never found a machine that can load/edit/run a large web app with decent performance. Oh yeah, and the latest SP causes it to crash *all* *the* *time*.
Fix it first, then improve it.