Microsoft addresses DevOps with InRelease technology

Microsoft has completed its purchase of InCycle’s InRelease business unit, announced in June, and is now deploying the software to offer DevOps capabilities to its Visual Studio and Team Foundation Server users.

The company has released an InRelease preview for Visual Studio of the company’s flagship software and has discussed how the software will be folded into Microsoft’s line of development software.

“The real interest in DevOps is about figuring out how to streamline the delivery of the software from the developer’s desktop to the production environment,” said Brian Harry, Microsoft technical fellow in charge of Team Foundation Server (TFS), Microsoft’s application lifecycle management product.

The emerging practice of DevOps seeks to shorten development time of software by having software developers work more closely with system administrators and other IT operations staff. The InRelease acquisition is providing Microsoft with a set of tools it can offer its customers to facilitate DevOps workflows.

DevOps came about largely due to the increased competitive pressure on companies and service providers to update their software. “We see the need for applications to be created faster and to evolve faster,” Harry said.

As a result, the release process for new software must be shortened as well. When software was updated every six months or so, an organization could devote a few additional weeks to vetting the new version before release. But if software updates come every month, the release process must be expedited as well, Harry said.

InRelease started as a series of scripts that InCycle developed to help the company automate deployments on behalf of its customers. InCycle is a Microsoft partner focused on integration work. “When the team had a new version of their code, it was costly and difficult to move it forward into production,” said Claude Remillard, president of InCycle software.

Over time, the company bundled its scripts into a general-use release management application, one closely integrated with Visual Studio and TFS.

With InRelease, project managers can specify the workflow process for moving an application from development to testing to deployment, handling tasks such as notifying managers who need to review, or otherwise prepare for, the software. InRelease can also install the software on the appropriate servers.

“The goal is that when we deploy into an environment, all the bits are on the servers required, so I can start running my code,” Remillard said.

By the end of the year, Microsoft plans to fully integrate the InRelease authoring components into the premium, ultimate and test professional editions of Visual Studio.

The InRelease server components will be integrated into Team Foundation Server 2013, also due later this year. The InRelease deployers, which are required to run on each deployment node, will be licensed separately.

By the end of the year, Microsoft will also ship its own version of InRelease, Harry said. Until then, the product can be purchased from InCycle, and those who buy before the Microsoft product is out will get a full upgrade to the Microsoft release.

Early customers for the InRelease software included banks, retailers and commercial independent software vendors. Another big user may be Microsoft itself, which just went through a reorganization in part to more quickly adapt to the ever-changing market for devices and services.

Already, the company has promised to deliver more frequent updates to Visual Studio and Windows Server. According to Harry, the company has started to use InRelease as a way to manage accelerated release schedules of a few of its products, and it will probably use it more as time passes, much in the same way that Microsoft development teams adopted TFS.

Microsoft's Visual Studio update addresses the connected app

Microsoft kicked off its Build conference in San Francisco this week by releasing a preview of the next version of its Visual Studio IDE (integrated development environment), as well as updates to other development tools.

 

“If you are interested in building a modern, connected application, and are interested in using modern development lifestyles such as ‘agile,’ we have a fantastic set of tools that allows you to take advantage of the latest platforms,” said S. “Soma” Somasegar, corporate vice president in Microsoft’s developer division, in an interview with IDG News Service.

 

Somasegar noted, for instance, how the new Visual Studio provides more tools to help developers build applications for Windows 8.1, a beta of which is also being released this week.

 

Microsoft is releasing a preview of Visual Studio 2013, the final version of which is due to be released by the end of the year. The company is also releasing Visual Studio 2012 update 3, and a preview of the .NET 4.5.1 runtime framework.

 

Many of the new features in Visual Studio 2013 address the kinds of mobile, connected applications that developers need to build these days, Somasegar said. For instance, it provides new tools to profile energy and memory usage, both of which must be considered when building applications for mobile devices. It also includes a new tool for providing metrics on how responsive an app is for users.

 

Visual Studio 2013 is also tackling the challenge of writing an application that relies on cloud services in some fashion. Microsoft is providing interface from Visual Studio to its Azure Mobile Services, which synchronizes data and settings for a program used across multiple Windows devices.

 

Visual Studio 2013 itself will also be easier to use across multiple devices. It will allow developers to define environmental preferences, or the settings and customizations for their own versions of Visual Studio, that then can be applied to other copies of the IDE. Microsoft can store these environmental settings in the cloud, so they can be downloaded to any computer connected to the Internet.

 

“People go through a lot of trouble to set up their environment. Once they go to a different machine, they must go through the same hoopla again to get to recreate the environment they are comfortable with,” Somasegar said. “Once you set up your environment, we store those settings in the cloud, and as you go to another machine, you won’t have to recreate your environment.”

 

Another new feature, called Code Lens, provides “a class of information that, as a programmer, has been historically hard to get.” It can show, for example, which part of a program is calling a particular method and what other methods that method calls. Visual Studio 2013 also expands its support for C++ 2011, the latest version of the C++ language. Visual Studio’s feature for debugging the user’s own code (as opposed to running a debugger against the entire set of code) now works with C++ 2011.

 

Beyond Visual Studio, Microsoft is building more developer hooks into the next release of its browser, Internet Explorer 11, which is expected to be released with Windows 8.1.

 

Microsoft has completed “a major revamp” of the tools the browser provides to developers. The browser will come with a source-code editing tool, as well as a number of built-in diagnostic tools, Somasegar said. The idea is that the developer won’t have to toggle back and forth between the browser and the IDE. A Web application or page can be run, and mistakes can then be fixed, directly from within the browser.

 

With .Net, Microsoft worked on improving performance of the runtime environment. It can also provide more diagnostic information on how much memory a .Net program is using, and provide more information in a dump report should a program crash. Also, once a developer chooses a particular platform for a .Net project, such as an ASP.Net project, .Net will only display the components that can be used on that platform.

 

Microsoft is also releasing a white paper that offers a road map of where .Net is headed. The paper will be “one cohesive document that talks about .Net as it relates to Windows, Windows Phone, Windows Azure,” Somasegar said. “It is a comprehensive document that shows people how to think about the future as it relates to their current .Net investments.”

 

When Windows 8 and Windows RT were introduced, many Windows developers voiced concerns about the future of .Net, due in no small part to how little the platform was mentioned in Microsoft’s initial instructions on building Windows 8 modern applications.

 

Somasegar said Microsoft has always encouraged, and will continue to encourage, the use of .Net as a way for developers to write “managed code” for Windows 8 and Windows RT modern applications, as well as for Windows desktop applications.

 

In addition to issuing previews of Windows 8.1 and Visual Studio 2013 this week, Microsoft is also releasing a preview of the latest edition of the company’s application lifecycle management software, Team Foundation Server 2013.