"Visual Studio 2010" promises a high developer productivity. The most important features and changes compared to VS 2008.
Immediately after the first launch of Visual Studio 2010's new logo is in the eye, for the .NET Framework 4.0 Visual Studio 2010 and has come up. Initial fears that in the IDE all previous visually compared to the upside was the will, but then quickly dispelled, as the successor to VS 2008 also presented in the usual objective look, a little modernized, and has only been sharpened contours.
Although Visual Studio 2010 for the first time is based on the Windows Presentation Framework (WPF), of which at least in the Professional Edition does not feel way too. The distance to Expression Blend, the second developer tool from Microsoft that is based entirely on WPF has been preserved. Obvious changes are there primarily to the Code Editor, changes can be done by holding down the Ctrl key with the mouse wheel by vector graphic representation of the font size. Also on the second successful and long-overdue innovation you will eventually come only by accident: Visual Studio 2010 supports more monitors connected by every window of the IDE from the main window can move freely across the extended desktop. Thus, it is finally possible to consider design and code view on two monitors.
More comfort on Code Editor
It is often the little things that developers of a new version of their favorite tools delight, in which we of course asked why they have not been previously introduced. This includes, in addition to improved docking behavior of the IDE window and the fact that the close button for a window recently next to the window title and not far away on the right side is, the ability to source code to be able to use types in the before they are defined. Following is a C # developer command :
Code:NewType nt = new ();
One has this harmless command in VS 2008 more then a compiler error resulted when the type NewType not exist. In 2010, the VS IDE via a Smart Tag selection list, that does not exist to define the type yet.
Collaborative debugging
What options the transition to WPF for a code editor, offers fact makes the show that the result of expressions during a debug evaluated are meeting, with a note ("DataTip") and is the little box can be placed in the free editor window. Also, breakpoints can be explained by such remarks. DataTips can, just like breakpoints, and exported to a developer colleagues will be made available, which works on the same project. Two other novelties will lead to more clarity in the source code: If you highlight a symbol name, all places where the name appears in the source code to be highlighted. If the cursor is placed on a method-member and from the context menu entry "Show call hierarchy" is selected, displays the Call Stack window, which methods to call each other. A particularly exciting feature for developers in VS 2010 called "Intellitrace"- at the start of the beta phase aka "Historical Debugger". Did you Intellitrace enabled in the options, the executed program sections in the form of recorded events, making it possible for a program interruption using the indicated in the margin Intellitrace symbols is to follow the code execution backwards by a recorded event is triggered. About Intellitrace context menu can be stated often invoked as a specific line or method and which commands have been executed before. Intellitrace should help that reduces development time significantly in larger projects. An interesting aspect arises here in connection with the "Microsoft Test Manager 2010". Users can associate a test run with a recorded Intellitrace log file, so that a developer by importing the log files can now drive those points in the source code, in which the tester has found a bug. Unfortunately Intellitrace only available in the Ultimate Edition of VS and works only with 32-bit managed code. Support for C + + , Microsoft, however, called into view.
Bookmarks