• Part 1 – Considerations
• Part 2 – Setup
• Part 3 – Configuration

• Part 1 – Considerations
• Part 2 – Setup
• Part 4 – Synchronizing Hierarchies from TFS

• Part 1 – Considerations
• Part 3 – Configuration
• Part 4 – Synchronizing Hierarchies from TFS

• Part 2 – Setup
• Part 3 – Configuration
• Part 4 – Synchronizing Hierarchies from TFS

Last week I was helping a customer get up and running with Lab Management. In an effort to make sure they’re up to date, I installed TFS and VS 2010 SP1 on their TFS machine as well as in all the Lab machines.

Notion Solutions is part of Imaginet, and last week Microsoft announced that Imaginet had won the Microsoft Partner of the Year in the inaugural Application Lifecycle Management category.

I was at a customer recently who have a small test database – around 120MB in size. I had encouraged them to use the DB Professional tools in VS 2010 to track their schema – that way they could deploy the database (as well as the latest schema) and some test data (through INSERT statements or even better, data generation plans). However, their developers didn’t have the time or skills (yet) to do this.

So you’ve got your virtual environment running and you’re deploying your application using the Lab Default Workflow. Only, you have a config file and you need to update a connection string or something in the config file for automated tests to run properly.

If you’re running Lab Management with lab machines with XP SP3, you may run into a problem where the Test Agent is never ready for running tests.

I am preparing for the demo at DevDays, and we wanted to run a Load Test using our Lab environment. However, when trying to access the performance counters on the lab machines, I got “Access Denied” errors. That lead to some searching on why this is the case.