VS ALM Library Updates on MSDN for October 2010

Patrick-MSFT

October has been spectacular here in the Pacific Northwest, which has nothing to do with the reduced output in this month’s MSDN Library updates for VS ALM. There is a lot of work being done to reorganize and refocus our content to make it even more useful to you in acccomplishing your goals. We are also working on feature packs and preparing for SP1. Okay, and some of us did go to the beach 🙂

We borrowed the Team Foundation SDK info from Allen Clark’s blog. Along with his work on the SDK, Allen writes about team projects and development processes such as agile and Scrum. His blog is also a great place to hear about our own documentation processes and ideas. Check it out.

As always, let us know what you think.

Patrick


This month’s updates:

!—->

Getting Started With ALM

Software Requirements for Visual Studio Application Lifecycle Management Features provides an overview of the versions of Windows, SQL Server, and SharePoint Products that are compatible with features for application-lifecycle management (ALM) in Visual Studio 2010.

Installing Team Foundation Server

Tim has added tips about upgrading TFS and TFS support for SQL Server clusters. You can read about them in his blog posts:

The information was also added to the Library topics:

Team Foundation SDK

We just published updates to the Team Foundation SDK, which now covers the server object model. We’re making some other changes, too. Of course, we’re adding more content to the reference material. For example, we’ve added information that we think you’ll find useful in Microrosoft.TeamFoundaiton.WorkItemTracking.Client Namespace, including a code snippet to help you get connected to a work item store. At the same time, we’re removing content that’s not all that valuable.  Extending Team Foundation and Extending Work Item Tracking used to have a lot of verbaige that primarily served the purpose of meeting some conventions that we have, rather than making it easy for you to use the topic. That’s been removed. In Extending Team Foundation, we also pulled up some relevant reference links alongside the links to conceptual topics, like this:

Bugs, tasks, and other work items

Samples and concepts

Reference

Testing the Application

Guidance for Build, Deploy and Test Workflows

What are your options for automating all or part of the build, deploy, and test process with Visual Studio? What do you need to accomplish these tasks?

How to: Create a Hyperlink to View Test Results From an Email

Add a hyperlink to an email for your test run results:

Lab Management

Configuring and Administering Lab Management

Expanding or Changing Your Virtual Lab adds information about moving System Center Virtual Machine Manager to a new server in two different situations.

  1. You began to use Lab Management on a pilot basis on temporary machines and now want to deploy the functionality to production servers. Because you are starting over in a production mode, it is not important to retain the environments, templates, and other lab assets you had been using during pilot testing.
  2. You have to change the server that is running SCVMM because of capacity or availability issues. Because you want to continue operating as before, you have to preserve the same environments and related assets.

Using a Virtual Lab for Your Application Lifecycle

We clarified information about the classes in the lab activities: Team Foundation LabManagement Activities

Creating Virtual Environments

We enumerated the operating systems you will need to install on VMs in order to support test agents in virtual environments.

!–content>

0 comments

Discussion is closed.

Feedback usabilla icon