Channels ▼
RSS

Database

Microsoft Shows Cadence In Visual Studio 2012 Update 2


Microsoft has released Visual Studio 2012 Update 2 this week and the product is now also available for download. This update is intended to improve Agile planning practices for software application development teams that want to keep their Visual Studio developers efforts in line with Microsoft's current cloud-hosted capabilities.

More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

With this release now emerging, Microsoft reminds us of its commitment to shorter release timelines (this lessens the learning curve and developer "upgrade shock" factor of course) as it comes just four months since Visual Studio 2012 Update 1.

Microsoft's developer division corporate VP S. Somasegar reminds us that Visual Studio 2012 introduced a wide range of capabilities focused on enabling Agile teams, not only for development but also for planning.

"With VS2012.2, Team Foundation Server (TFS) has been augmented with an additional variety of features to help make it even easier for Agile teams to do their planning, in particular around adapting to a team's preferences and work styles," he said.

Somasegar continues, "For example, VS2012.1 introduced new project tracking options, including a Kanban board and a cumulative flow diagram; VS2012.2 augments those experiences with the ability to customize the Kanban board to adapt it for an organization's needs."

Alongside the Kanban update are so-called Work Item Enhancements; i.e., the Send Email in Web Access function allows team members to share Team Foundation Service work items through email from the web portal — and Tags also exist here to let teams add their own metadata to work items.

Microsoft stresses the quality enablement factor here. You know when the firm labels Quality Enablement in CAPS, the marketing function want us to try and leave that in. What it means is that Visual Studio 2012 is now more closely engineered to enabling quality to be maintained and improved throughout development cycles.

"This focus can be seen not only in the RTM release, but also in VS2012.1, with the added support for code coverage with manual ASP.NET testing, with support in Test Explorer for custom 'traits', with support for cross-browser testing, and with improvements to Microsoft Test Manager," said Somasegar.

Profile Unit Testing also exists at this level to provide instruments for both unit testing code and customer code, which present the results in a single profile report.

Microsoft's next "improvement category" here (yes CAPS letters again) is what has been labeled line of business development (presumably LoBD). So this incorporates the option to use Microsoft LightSwitch to build cross-browser and mobile web clients with HTML and JavaScript. There is also support to target SharePoint 2013 and Office 365 — and it includes support in Blend for SketchFlow, WPF 4.5, and Silverlight 5.

NOTE: Microsoft LightSwitch is described as a simplified self-service development tool that enables you to build business applications quickly and easily for the desktop and cloud.

Finally, we come to where this product has been ramped up for better developer experiences. Microsoft suggests that Visual Studio has to be as "streamlined" as possible given the amount of time developers spend inside the IDE.

With this in mind Somasegar points out that Code Map has been updated with improved responsiveness as well as with debugger integration, providing a visual perspective on the relationships and dependencies in code being debugged.

"Symbol loading has been improved across both the profiling and IntelliTrace experiences. The Workflow designer now has an improved debugging experience. The XAML design surface in both Blend and the Visual Studio editor includes multiple performance and reliability improvements, in particular when loading large projects and when using third-party controls," concludes Somasegar.


Related Reading






Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dr. Dobb's encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dr. Dobb's moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing or spam. Dr. Dobb's further reserves the right to disable the profile of any commenter participating in said activities.

 
Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
 

Video