Learn to use Visual Studio, Visual Studio Online, Application Insights and Team Foundation Server to decrease rework, increase transparency into your application and increase the rate at which you can ship high quality software throughout the application lifecycle
We have just published the CTP1 for Visual Studio Release Management 2013 Update 3. You can download this release here and read through the KB article here.
With this update, you can use DSC (Desired State Configuration) to deploy apps to your environments. Using DSC, you can run Powershell scripts on target servers of an environment without having to install the deployment agent. You can deploy to both on-premise environments as well as Azure environments. A detailed walkthrough of using DSC to set up a release management template is provided in the attached tutorial document.
Note that this is a CTP, and is not go-live. Do not upgrade your Release management production servers to this version. So, go ahead and give this a try on your demo/trial machines, and let us know what you think.
Here are some useful links to get you going.
Release with ease and fun in different environments!
How will this affect environments that are already configured using DSC in a "Pull Model" set up? Are the agentless DSC actions done using the Push model? if so how will someone be able to resume the pull model once configurations are Pushed via Release management DSC agentless deploy?
I get an error when I download the server component (Release Management Server for Team Foundation Server 2013 with Update 3 CTP 1 (x64) - Web Installer (English)) and try to install it on a clean, Windows 2008R2 standard server (4GM Ram, 64bit,dual 2.6GHz Cpu):
Problem Event Name: APPCRASH
Application Name: en_release_management_server_for_team_foundation_server_2013_wit
Application Version: 12.0.30516.20
Application Timestamp: 535fef1c
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7601.18229
Fault Module Timestamp: 51fb1072
Exception Code: c0000005
Exception Offset: 00038e19
OS Version: 6.1.7601.2.1.0.272.7
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
If the online privacy statement is not available, please read our privacy statement offline:
Windows 2008R2 standard server (4GM Ram, 64bit,dual 2.6GHz Cpu) is a supported configuration hence it should work. Can you please share the install log from the %temp%\dd_rm_Server*.* file?
And also can you try vs2013.3.ctp1_rm_enu.iso after mounting it?
Hi, I worked it out. I was running it as myself, instead of as an administrator. I guess it would be nice to update the installer so that it displayed a nice message that the installation needs to be run as an administrator?