The previous article mentioned an artifact called ReSharper, Powerful, coding efficiency and code quality that is rubbing up, but the biggest problem of the artifact is too expensive resources, every time the system prompts for insufficient memory, that call a tangled ah. So every time the new VS release can not help to see whether to enhance the editing function, can not help to discuss, this time VS2015 is no exception.
When Microsoft released Roslyn last year, Microsoft had released an "early adopters" version of the VS editing enhancements, just refactoring (reflector), saying that this is too useful for control development, but only the tangled resharper before, although it is not very complete, was also encouraged "Crowds" go to the Microsoft Feature collection site on the crazy dot support it. A year in the past, Microsoft formally named Roslyn as the. NET compiler platform (. NET Compiler Platform), thanks to this platform, Microsoft has perfected the editor enhancements that delight developers in VS2015.
-
- support for temporary variables and local variable refactoring, you can easily replace a block of code with a temporary variable, or in turn, put the execution block of the temporary variable back.  
-
In addition to the refactoring feature above, Microsoft has also done other editor enhancements, mainly for touch device support, high-resolution device support, and so on, before encountering any problems, these are nothing to press the table, but for JavaScript editing enhancements are very competitive, such as better navigation, Using JSDoc to improve smart hints, code folding and so on, think of that good thousands of line of the Wijmo widget implementation, altogether think now "ape" are very happy.
As a great "program ape" member, only editor enhancements are not enough to look at, but also the desire for a good debugging and diagnostic tools, has always been doing well in this field, but there are some of the pain so that the vast number of "apes" are disturbed, of course, the good news is that VS2015 again enhanced debugging and diagnostic tools, So that we can find the crux of the problem more calmly and accurately. Let's take a look at these other development environment envy, once very tangled function point it:
- Additional debugging when editing execution (edit and continue on Attach), think of the countless times to fix some small problems, also changed a few words, want to see the effect, you have to wait for the IDE to stop the current debugging, and then compile in the start of the new debugging, each time does not seem to spend more, The cumulative effect is really amazing, so editing the executive function is pretty cool for complex development scenarios. Today, vs adds support for editing execution of additional debugging, which is useful for many web development, for example, when you use C1 Studio for in your page. NET Web control, put it on IIS, and found that the problem may be that a property is set less, now you just need to attach debugging IIS, and then at the right time through the editing of the execution of the code to inject in it.
- Performs a lambda in the debug window. For example, returning an entity from EF, and then hanging a bunch of LINQ locally, debugging to half, to see if the intermediate results are expected, happy to monitor (watch), immediate execution (Immediate) and other windows pasted a piece of code, enter, look forward to a good time, the IDE prompts Lambda , can not continue, think it is very uncomfortable.
- XAML UI Debugging tools, after so many years of development, WPF is also a foot in the interface layer, but the IDE for the interface debugging this piece has not improved, many tools are stuttered, not the performance problem is not interactive, specifically, such as C1 XAML FlexGrid, The boss suddenly jumps out to let you explain the custom editor that's what, it's really hard to say clearly. VS2015 provides two widgets for this: Live Visual tree and live property Explorer, which opens the interface to debug many details on the interface in real time, such as element placement, binding details, and so on.
- Another function point of WPF is the Timeline tool, which replaces the previous generation of the XAML UI responsiveness tool, a bit like the timeline in the developer tools provided in WebKit, which expands the performance of the application on a timeline. For the performance tuning of WPF, it was timely, more than a little bit better than the earlier performance tool.
Of course, the actual VS2015 also provides additional efficiency and quality enhancements, confined to space, which is not covered here, and interested children's shoes can be discussed together.
Next we'll talk about asp.net~ please keep your eye on it ~
Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.
Visual Studio 2015 Express (2)-Improve efficiency and quality (VS2015 core competencies)
