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
Updated 7/16/2012: Please note this an archived post and the Lab Management VHD has been retired and been removed from the Microsoft Downloads site.
Merging the Lab Management blog and bringing over the last post from Vijay as the steps should prove helpful for people wanting to do this with the Beta VM.
With the release of the Visual Studio 11 Developer Preview we released the Virtual Machine with Visual Studio 11 Developer Preview bits and described 6 hands-on-labs that can be tried in that virtual machine. This post will show how you can use the same virtual machine in order to try out an additional walkthrough for Lab Management.
In this walkthrough, we will:
Before going through this walkthrough, ensure that you have:
Install additional software and create additional assets
Create a standard environment
Create and run a Build-Deploy-Test definition
In this walkthrough, you have seen how easy it was to create a standard environment. The process of installing agents onto the machines of the standard environment is automated. You also saw how you can run a build-deploy-test workflow using a standard environment. These are some of the enhancements in Visual Studio 11.
In the walkthrough, you have used the same machine for creating the standard environment. In a more realistic scenario, you would typically have test machines that you would compose into an environment. Accomplishing that using the VSALM machine can be done as follows:
Create another virtual machine with Windows 2008 R2 operating system, joined to workgroup, and present on the same Internal Network on the same Hyper-V host. We will call this virtual machine as "Test Machine" in the following description.
When you setup this machine, ensure that the Administrator's password is the same P2ssw0rd.
On the Test Machine, edit the C:\windows\system32\drivers\etc\hosts file. Add an entry <IP address of VSALM Machine> www.fabrikam.com to the hosts file. This is required for the test machine to be able to find www.fabrikam.com.
Ensure that the Network and File Sharing exception is enabled in the Firewall settings for the Test Machine.
The project that comes with the VM is an MVC project. In order to run MVC tests on the Test Machine, you need to install additional software on it. (E.g., Visual Studio with MVC3. Or, if you are like me, and are ok with the test run failing, then skip this step :). You can always do it later.).
From Microsoft Test Manager, create a new Standard environment. This time, provide the computer name of the Test Machine. In the wizard, select the 'Advanced' tab, then select the option to run Coded UI Tests. This will cause the test agent to be run using the provided account and authenticate successfully with the test controller.
Once the environment becomes Ready, queue the same Build-Deploy-Test definition on this environment.
Thanks @Charles_Sterling for this helpful post but, first you have a broken link "Visual Studio Agents 11 Developer Preview ISO"
Second I just wander why you didn't perform this post on the new VM and new bits of Visual Studio 11 Beta not Visual Studio 11 Developer