Over a million developers have joined DZone.

Visual Studio 11 and DevOps Crossing Paths?

DZone's Guide to

Visual Studio 11 and DevOps Crossing Paths?

· DevOps Zone ·
Free Resource

Learn how integrating security into DevOps to deliver "DevSecOps" requires changing mindsets, processes and technology.

The folks at Redmond have released some juicy new details about their latest version of Visual Studio that's set to go into beta on February 29th. It looks like Microsoft has been feeling the DevOps vibe of late and have taken action to implement tools that allow developers and operations personnel to frolick together (much like Puppet and Chef) in Visual Studio 11 projects.  Major integrations with other "Ops" tools that Microsoft produces is a big part of this.  Michael Crump shares his thoughts on some of the changes over in a post in our .NET Zone.

In the past, one of the gripes that devs had was getting some sort of "actionable feedback" from the guys (or sometimes girls) at the operations staff about their programs. By embracing DevOps (and noticing the serious trend), Microsoft is joining the movement to try to shorten that distance between the two groups so programs can be deployed quickly and with fewer bugs.  They've already created a good deal of agile-focused tooling that fits right into the DevOps philosophy, but more is being done in today's announcement.

One of the ways Microsoft is trying to encourage DevOps is a to integrate a bridge to Microsoft System Center 2012, which is a mangement tool used by operations that also collects diagnostic information that can help developers track down and squash bugs. This is actually really cool because, on the user end, operations can work with System Center, which is familiar to them, and devs work with Visual Studio, which is their cup of tea. But of course, it's important to note that DevOps is also about company culture, so these tools won't save you if your communication situation sucks.

Another tool being integrated is a newer version of VS's IntelliTrace for operations, which is a live debugging aid that can be planted with the operational program itself.  This means that a trace log leading up to a crash can be extracted from a production server, even if Visual Studio isn't on the server. Operations can then shoot this summary over to the devs, who can analyze the file in Visual Studio.

Microsoft seems to be knee-deep in the DevOps movement, even claiming that they've been using the philosophy to build Visual Studio itself. So as a developer or member of an operations team, do you think this will lead to less headaches and more polished releases?

Get the Beta next week to find out!

Learn how enterprises are using tools to automate security in their DevOps toolchain with these DevSecOps Reference Architectures.


Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}