today I want to give you some information about the Microsoft Visual Studio 20010 (code-name “Rosario”) and .NET 4.0. The first pre-release for the Community Technology Preview (CTP) was released on 31 october 2008. The mains news introduced in this version are:
- full UML support for improving communication between Architects and Developers
- build improvements for avoiding ‘broken builds’ and increasing the build realibilty
- coder UI Tester for recording the right UI behaviours and automatically generates code for testing it
- hystorical debuger for decreasing the effort spent during debug sessions
- tester activity center for avoiding the famouse “it works on my machine”
You can also visit the VS2010 Web Site for more information.
Microsoft Visual Studio 20010 provides fully UML support. This functionality can be used for increasing the communications between developers and architects and avoiding miss-understanding.
How many times developers say to theirs project leader: “hey, we implemented this behaviour in this manner as we decided… so don’t tell me I make wrong implementation!” ?
So, thanks to support of: use cases, sequence diagrams, activity diagrams, logical class diagrams and component diagrams every miss-understanding can be reduced.
The UML is support both for modelling entities and then generating the relevant code and both for generating UML diagrams from the code itself!
VS2010 - Component diagram
VS20010 - Sequence Diagram
Microsoft Visual Studio 2010 uses the Workflow Foundation for improving the build process: all the MSBuild operations can be defined in a visual way with the ‘activities’ more understandable to human, avoiding put your hands directly on xml files.
Two more builds system are available: Gated Check-in and ShelveSet Check-in. The Gated Check-in ensures to a single developer that everythinghe done is ok before performing the check-in. The ShelveSet Check-in is quite similar, but in a global way, a new ShelveSet containing all the developers check-ins is created and ensured to not ‘broken the build’ after performing the real check-in.
VS2010 - Build System
Coder UI Tester
The idea is to record what we are doing over an user interface and describing the right UI behaviours. For example you can record a push button action than you can put the behavioud: “Clicking the following button results in enabling this checkbox”. So recording an action and describing the correct result the VS2010 automatically generates a code for testing your applciation!
VS2010 - Coder UI Tester
How many times a poor developer said: “Ouch! The value of this variable is changed right now but… what is the prevoius value? I have to debug it again!”. With VS2010 the effort spent in debug is decreasing thanks for the hystorical debug! Every time a method is executed it is registered on the stack, and double clicking on it you can view all the prevoius values of locals variables. Here you are a screenshot:
VS2010 - Hystorical Debug
Tester Activity Center
For increasing the communication between testers and developers, Microsoft Visual Studio 2010 introduced a new application for managing the test cases and logging in a developer friendly way the results. This avoid the well know phrases usually said from developers such as: “It works on my machine!” or “I do the same thing the tester said but I have different result!”. This more cooperative information provided in testing phase by this tool are: Action Log, Event Log, System Information, Debug Information and Video Recorder too!
This tool also provides reports.
VS2010 - Testing Tool
VS2010 - Tester Video Record
VS2010 - Tester Report