|DevOps is an increasingly important part of application lifecycle management and is a growing area of interest as businesses need to develop and deploy quality applications at a faster pace. As part of this increased focus, Microsoft has introduced Release Management for Visual Studio 2013, a solution for .NET and Windows Server applications.
Essentially the tool makes use of scripts and actions to do the heavy lifting for releases, but also captures the people workflow in the process i.e. who needs to approve a certain step. Furthermore, Release Management plays nicely with both on premise and cloud based servers. There are 24 hands-on-labs for you to take a scripted approach towards learning this content. These labs double as demo scripts in case you want to show off these features to others.
Why not try out these virtual labs for yourself? You can get started here. Additionally you can take this Microsoft Virtual Academy Course on the role of DevOps in Visual Studio Release Management. This course will equip you with the necessary skills to build an effective release pipeline with the Release Management functionality provided by Visual Studio and Team Foundation Server.
If you want to learn more about automating your deployments with Release Management, read this article on MSDN. Additionally, you can gain a full overview of Release Management by checking out the website here.
In other MSDN Subscription news, Technical Support incident pooling is now avaiable in the APAC region. Incident pooling enables you to combine and share Technical Support incidents across all of the MSDN subscribers within your organization. This provides a better experience by enabling you to consume your Technical Support incidents more efficently.
Also, SQL Server 2014 is now licenced with Team Foundation Server 2013. This means that you can now use one instance of SQL Server 2014 Standard software as your Team Foundation Server 2013 database. This means that uses of LOB applications or other ALM tools that access Team Foundation Server through a pooled connection (i.e. a single shared account) no longer need to be licensed with a CAL. This will enable customers to adopt TFS without abandoning tools that you are using today.