Today I have released Team Deploy 2010 for Team Foundation Server 2010.  In this post, I am going to give a quick overview of Team Deploy if you haven’t used it before, explain this release and upcoming releases, compare it to Lab Management 2010, and give a walkthrough for setting it up and uninstalling it.

What is Team Deploy?

Team Deploy is a set of custom build activities used to deploy MSIs to multiple client PCs and/or deploy services to servers.  This activities include the ability to kill processes, start/stop services, pass in arguments to the MSIs, provide the service username/password, and uninstall previous versions.  Team Deploy uses SysInternal’s PSTools to remotely execute MSIEXEC to install the MSIs and PSKill to kill processes.  By using Team Deploy, development teams can create automated build and deploy processes for better configuration management.  Deployments can be done on demand or scheduled just like any other build in Team Build.  If you are using Team Foundation Server 2008, Team Deploy 2.1 is the current release to download.  Team Deploy is open source and free to use.  It can be downloaded from http://teamdeploy.codeplex.com

This Release and Future Plans

I am calling this version of Team Deploy 2010, Release 1.  This release is a 1 for 1 port of the MSBuild tasks to Workflow custom activities.  I wanted to release this version without any additional enhancements so development teams can upgrade their build definitions to workflow.  I have a lot ideas for future versions.  Lab Management 2010 has given me some ideas (see comparison below) and there are several other things I want to do.  Here is a list of some:

• MSI Package for Team Deploy 2010 – For custom build tasks, deployments are easy.  Basically just copy the Dll to the MSBuilds folder and use that path in the build definitions.  For Team Build custom activities, it is a little more complicated.  As you will see in the Setup Walkthrough below, there are several steps that are fairly easy to do manually but are going to be more difficult to do with a custom task.  I have begun working on this but it wasn’t ready for this release.
• Breakout Deploy activity into Workflow – Currently the Deploy activity does all the work and calls the other activities within code.  I want to create an additional workflow with all of these steps in a workflow.
• PowerShell capabilities – PowerShell 2.0 has the ability to be run on remote machines.  I want to research this functionality and see if it makes sense to create an addition set of activities that use PowerShell instead of PSTools.
• Custom Build Definition Screen – Display screen to create the deployment options through the UI instead of creating it in XML today.
• Change the Threadpool to .Net 4 Tasks for deploying to multiple machines at the same time.
• Team Deploy build definition to call another definition to  do the build and deploy (Similar to Lab Management)

Team Deploy and Lab Management

Visual Studio 2010 introduces an additional product for Team Foundation Server 2010 called Lab Management 2010.  This product allows virtual environments be created, quickly provisioned, used for manual and automated testing.  Lab Management also includes a new build definition type and activities.  With the build definition type, it allows you to revert the virtual environment to a baseline snapshot, build the application, deploy the application, run the automated tests, and capture the results.  So Lab Management can do what Team Deploy can do and a lot more.   The one area that I have seen Team Deploy used where Lab Management would not be used is for deploying applications to QA and Production.  I have worked with several companies that use Team Deploy to deploy to all of their environments for a consistent deployment process.

Team Deploy Setup

Here are the steps to install Team Deploy and create a simple build.

1. The TeamDeploy2010_R1.zip file contains the following 4 files that are used to install the application.

2. Copy TeamDeploy.Activities.* to a location in source control and check in.

3. Add TeamDeploy.Activities.dll to the GAC using Gacutil.

4. Add source control location of custom assemblies to build controller.  ($/TestBuilds/CustomActivities in this example)

5. Copy DeployTemplate.xaml to source control in the BuildProcessTemplates folder.

6. Create a new build definition.  In the Process Step click on “New” Template and add the existing DeployTemplate.xaml template that was added to source control.  Click OK.

7. Set the build properties to where the PSTools is installed and where the deployment XML is located. Click Save.

8. Rename and edit SampleDeployScript.xml to specify applications to install and machines to deploy to.  See http://teamdeploy.codeplex.com website for full list of options available. If you open the DeployTemplate.xaml.  It should look like this. 

If there is an error for the deploy activity.  Delete the AgentScope activity.

1.  Add Team Deploy 2010 Activities by right clicking in the toolbox and select “Choose Items…”. Make sure System.Activities Components tab is selected and select “Browse…” to find the location of the TeamDeploy.Activities.dll and choose it.

  2. Once you have added the TeamDeploy.Activities.dll, you will see the activities selected.  Click Ok.

3. Clicking Ok will add the activities to the toolbox. Drag the Deploy activity to the AgentScope container.  The required properties will cause a red error icon to display.  Fill out the properties to where you have the deployment script and PSTools installed. (Sometimes the designer won’t let you drag the Deploy activity to the canvas.  Save the workflow, exit Visual Studio 2010, and reopen the workflow.  It should then.

Uninstalling or Updating Team Deploy 2010

1. Close Visual Studio 2010

2. Stop the Visual Studio Team Foundation Build Service Host service.

3. To remove Team Deploy from the GAC, browse to c:\windows\microsoft.net\assembly\gac_msil and delete the TeamDeploy.Activities folder.

Build Log of Deploy activity in Team Build 2010

Here is an example of the build log for the Deploy activity.

I hope you enjoy!  Let me know if you have any ideas or run into problems.

Mike

Thanks everyone for coming on Tuesday to the Omaha Team System User Group meeting to see my presentation on What’s New for Testing in Visual Studio 2010 and TFS 2010. It was a great turnout and there were a lot of great dialog and questions asked.

Here’s the slides from the presentation.
http://www.codesmartnothard.com/content/binary/Whats_New_for_Testing_in_Visual_Studio_2010.zip

If you missed it or know anyone else that wants to see it, I’m doing this presentation again on a Webcast on April 14th at 11:00 (central time). Here’s the link:
https://www.clicktoattend.com/invitation.aspx?code=146828

Contact us below if you would like more information about implementing Team Foundation Server and/or Visual Studio Lab Management 2010.

Thanks,
Mike

I’m excited to be speaking 3 times in the next month on the new testing capabilities in Visual Studio 2010 and TFS 2010.  Two events are listed below.  The third event is full.  I hope you can make one of them.

Sign up for the Deliveron Newsletter to be notified about future presentations.

Presentation Overview

Visual Studio 2010 introduces Lab Management 2010 and Test Professional 2010 to remove the silos between QA professionals and developers to establish a more cohesive development and testing process.  Together these products include tools and features for creating test plans, creating and running manual tests, automated UI testing, creating test virtual environments, recording manual tests, and collecting diagnostic and error data to easily include with bugs.  See how everyone on your development and testing teams can take advantage of these improvements

Omaha Team System User Group Meeting

March 23, 2010 at 6:00pm
Farm Credit Services of America
5015 S 118th St
Omaha, NE 68137
Register here

Deliveron April Webcast

April 14th, 2010 at 11:00am Central Time
Register here

To me there has always been a feeling a of excitement to be able to build an application and then deliver it to someone that wants it. When I first started programming over 20 years ago with GW-BASIC on my Tandy 1000 EX, it was limiting that what I built could only be run within GW-BASIC since it was an interpreted language environment and not compiled. When I bought Quick Basic 4.5, I could finally compile my applications into an EXE and run them outside of the interpreter. Then I felt like I hit the big time when I was able to build my first setup package in Visual Basic 4. I remember I built a Hello World caliber application and created a setup package that took 3 or 4 floppy disks. I didn’t think it could get any better than this :) Over the years the the excitement about delivering applications became more from the what was built and not how it would be delivered. Visual Studio has always included functional, no frills setup projects. 3rd Party vendors have created easier to use and more power tools for creating deployment projects such as InstallShield. Developers who didn’t purchase a 3rd Party tool were limited to using the OOB (out of the box) setup projects within Visual Studio. While this is functional, the developer has to know where and how to do things and the usability is not very intuitive. It requires many steps to creating a MSI that I have blogged about in Deployments with TFS Part 2: How to create an automated deployment MSI. In Visual Studio 2010 there is finally an easy to solution without purchasing an additional production.

Last week I saw this post from Somasegar on Building setup and deployment packages in VS 2010. Microsoft has partnered with Flexera, makers of InstallShield to create InstallShield Limited Edition for Visual Studio 2010. This brings the InstallShield graphical interface to Visual Studio. In addition to providing a highly intuitive interface for building setup packages, this product allows setup packages to be built from with TFS Team Builds. This has been a major pain point for automated deployments and SCM (Software Configuration Management) processes. I downloaded and installed InstallShield 2010 LE and here is a walkthrough of the tool.

Download and Installation

Read Somasegar’s blog post on how to download and install it. (see link above)

InstallShield 2010 LE Setup project

Once it is installed and you create a InstallShield Setup project, the Project Assignment view is the default view. As you can see, the graphic is a guide that explains the parts of the MSI and the steps to create the package. At the bottom of the screen are the steps to the installation project. In addition to the steps at the bottom of the guide, there are also intuitive steps to the right that keep all of the package settings cleanly organized.

This first step is to fill out the basic information about the application that is going to be deployed.

In the second step, required operating systems and prerequisite applications can be specified and enforced when installing the application. Custom prerequisites can be defined by choosing “Create a custom software condition” under “More Options”.

The installation Architecture section step is disabled in the Limited Edition. In the other editions different features can be defined for users to choose what sections they want installed.

The next step is the Application Files. Here the application’s files can be added to the installation. The “Add Project Outputs” is the primary button for adding the application files. I found this dialog window to be a lot easier to use than the Visual Studio setup project.

The Application Shortcuts step is where desktop and start menu shortcuts can be defined.

If the application requires any registry entries, they can be defined in the Application Registry step.

The last step is the Installation Interview. This step asks a series of questions that drive what dialogs the user running the installation will see. Custom dialogs are not supported in the InstallShield Limited Edition. Custom dialogs are supported in the Visual Studio setup projects. For the automated deployment MSIs, I create a dialog that allows the user to specify the environment.

Custom Actions are non-standard activities that can be performed at different points of the installation process. The Limited Edition supports VBScript, JScript, and Exe custom actions. However, as shown in the following image, there are only a couple points in the process where custom actions can be defined. The Premier and Professional editions also support InstallScript, a powerful scripting tool to create more advanced customizations to the installation process.

After I built the MSI, I ran package to install it. Users will see this message box that the installation was created with a beta version of InstallShield.

InstallShield 2010 LE for Visual Studio 2008

The InstallShield 2010 LE Installation also installs a version that works within Visual Studio 2008. This interface looks the same in Visual Studio 2008 as it does in Visual Studio 2010.

Building MSIs with Team Build 2010

This is the feature I am most looking forward to in InstallShield 2010 LE. Standard Visual Studio 2008 setup projects can not be built within Team Build without some tricks. Unfortunately TFS Source Control and Team Build integration is not available in this beta version. I verified this with Flexera. They are currently working on it. As soon as an updated version is available with this enabled I will do a follow up post detailing the TFS Source Control and Team Build experience. I’m interested to see the following in action:

• Triggering a build and having the MSI compile with the updated assemblies.
• Curious to see if the InstallShield Setup project build can detect new dependencies added. My tests will include adding a reference to the primary output application. Then do a new build to see if the MSI will automatically include it. It might be expecting too much but this would be very beneficial.

Overall

• The Project Assistant is a very simple to use series of steps to create a complete setup project. As users feel more comfortable with the too, they will probably jump to the specific screens they are looking for in the navigation pane on the right. Both are highly intuitive and significant improvements over the the standard Visual Studio setup projects.
• Most things that are supported in the standard Visual Studio setup project can be accomplished with InstallShield 2010 Limited Edition. For most installation packages, these limitations will not be problem. However, I will not be able to create automated deployment MSIs because of the limitations of no custom dialogs and not being able to create custom properties.
• Being able to rebuild the MSIs during each Team Build is a huge benefit. Once this feature is available, I think it will become my favorite feature.
• I believe Microsoft and Flexera will both win with this product. Microsoft’s Visual Studio 2010 will include an improved tool for creating installation packages without having to reinvent the wheel. Flexera has built an amazing and easy to use product that will work for the majority of scenarios, but many will want to upgrade to the Express, Professional, or Premier editions to get the full power of InstallShield.
• The final product should be great, but this beta version is not ready to be used for more than evaluation purposes. Between the beta message box that is displayed when the user installs it and the fact that the TFS Source Control and Team Build integration features are not available yet, I recommend waiting until the final version is released.

Mike

There is a lot of information about the major updates of TFS 2010 and Team Build 2010 including changing from MSBuild to Workflow and Gated Check-Ins to name a couple.  In using TFS and Team Build 2010 beta 2, there are a lot little features and improvements that help make these two products complete and polished.  Here are a few of the features and I keep discovering new ones each time I use it.

New Build Definition will default name and solution to build

if you have a solution open in Visual Studio 2010 when you create a new build definition, the build name will default to the solution name.

An open solution will also automatically be populated as the Project to Build

The build retention policy is not set to “Keep All” by default.

Finally, the default retention policy for the builds is not set to “Keep All” anymore.  Primarily all results will default to keep the last 10 builds.  In Visual Studio 2008, I always recommended that this should be changed.

TFS Build notifies you about successful and failed builds

The Team Foundation Build Notification tool used to be part of the power tools.  Now it is included with the standard installation and alerts you to the success or failure of the build.   This supports continuous integration and gated check-in builds.  The notification dialog window also has an option for unshelving failed gated check-ins.

This dialog displays for a successful Gated Check-in build

This dialog is display when a Gated Check-In fails.  Notice the Unshelve Changes option to retrieve the changeset that was be attempted to be checked-in.

Build Parameters are now strongly typed and visible

In Team Build 2008, parameters could be passed in to a build when it was being queued.   However the format was command line argument style passed into a textbox similar to this:

/p:IsThisCool=”false”

In Team Build 2010, the build parameters are displayed as strongly typed properties.   This will allow for type checking and eliminate the misspelling of parameters.

Enjoy all of the great new features in Team Build 2010 including these smaller but helpful features!

Mike