Multiple output MSIs, different test machines?

Dec 21, 2010 at 3:39 PM
Edited Dec 21, 2010 at 3:39 PM

Our MSBuild script produces MSIs for two different products; SetupA.msi and SetupB.msi. Now we want SetupA.msi to be installed on machine Test_A and SetupB.msi on machine Test_B.

Does Team Deploy support this?

<?xml version="1.0" encoding="UTF-8"?>
<DeploymentScript>
  <DeploymentSteps>
    <CleanupPsExec />
    <KillProcess name="MyApp.exe" />
    <MSI>
      <UninstallProductCode>{11111111-1111-1111-1111-111111111111}</UninstallProductCode>
      <MSIPathFile>\\share\Builds\SetupA.msi</MSIPathFile>
      <OverrideDefaultArgs></OverrideDefaultArgs>
      <ExtraArgs></ExtraArgs>
    </MSI>
    <MSI>
      <UninstallProductCode>{22222222-2222-2222-2222-222222222222}</UninstallProductCode>
      <MSIPathFile>\\share\Builds\SetupB.msi</MSIPathFile>
      <OverrideDefaultArgs></OverrideDefaultArgs>
      <ExtraArgs></ExtraArgs>
    </MSI>
  </DeploymentSteps>
  <TargetMachines>
    <!-- How do I decide where A.msi and B.msi go? -->
    <TargetMachine name="Test_A" />
    <TargetMachine name="Test_B" />
  </TargetMachines>
</DeploymentScript>

Coordinator
Dec 21, 2010 at 5:22 PM

Hi,

Great question.  At one time I was going to modify the schema to handle more complex scenarios like the the one you have explained.  I however opted to keep the XML simple and handle this by creating a deployment script for each server when the installations are different.   In the build script then call the deploy task twice, one for each script/server.

I hope this is an acceptable solution for you.

Thanks,
Mike

Dec 22, 2010 at 8:30 AM

Hi,

Thanks for your prompt answer! I believe this is an acceptable solution. Thanks!