visual studio ultimate 2013 requirements

Selecting a sort property twice results in a descending order sort: Users can sort the defect list by six common properties or reset the list to its default sort order. Visual Studio 2013 adds support for sorting to the new viewer by way of a new toolbar Sort button. One key feature of the error list that was missing in the new viewer was the ability to sort the defect list. It also provides a detailed explanation of the code path for some warnings. Visual Studio 2012 moved code analysis results out of the error list and into a new Code Analysis Viewer that makes it easier to read and filter results. Users can still use the search box to separate errors from warnings. By design, this button replaces the Error/Warning option that was in Visual Studio 2012.

Users also have the option to filter the results by category using the search box, or select a specific category from a new dropdown button. Users will immediately notice the new categories because they augment the results displayed in the code analysis viewer: With this change, users can focus their efforts on the categories that are most relevant to their needs. Categories are particularly helpful when dealing with a large list of warnings, which can be overwhelming without some guidance on which warnings to focus on first. These categories provide a more fine-grained grouping of defects to indicate, for example, if the defect is related to an annotation syntax error, a critical security vulnerability or a simple logic error. Visual Studio 2013 introduces categories for native rules and exposes the existing managed code analysis categories in the user interface.

Users can now sort results by various properties including Rule ID, File Name and Category.

Categorization of results and enables users to filter by category.

In Visual Studio 2013, our focus has been on fixing bugs in response to user feedback, and making a few more improvements to the user experience. We made code analysis available in more editions of Visual Studio, introduced a new user interface for viewing, filtering and stepping through results, and made accuracy and other improvements. Last year’s release of Visual Studio 2012 marked a significant update to the Code Analysis experience in Visual Studio. This post (addressing uservoice feedback on CA) was written by Nat Ayewah, a member of the code analysis team in Windows

Visual studio ultimate 2013 requirements