Deploy BizTalk application msi (created with BTDF) via msiexec

Question

We are setting up deployment automation for our BizTalk MSIs that were created with BTDF.

Currently the approach we're working on is by calling msiexec from our deployment toolset. However, we need to install the application in a different folder than the MSI is set to propose.

The BTSF WiX default to C:-drive, whereas we must install to the E: drive. I have tried changing that in the msiexec call, but when passing INSTALLDIR or TARGETDIR, it just throws the msiexec help dialog in my face.

So I figured I should try and take a look at WiX, so that we could build the MSI to default to E: (if available), which would ultimately have the same end result, but WiX is a bit of mystery to me and it seems to have a lot of 'magic' for my understanding at this point.

BTDF by default uses the below structure (and mainly the lower portion of it), and I figure I would have to do something with the TARGETDIR and/or SourceDir. But I can't put my finger on which part is just some kind of variable that can be set.

<Directory Id="TARGETDIR" Name="SourceDir">
  <?if $(var.CreateStartMenuShortcuts) ~= True?>
  <Directory Id="ProgramMenuFolder">
    <Directory Id="BizShortCuts" Name="$(var.ProductName) $(var.ProjectVersion)">
      <Directory Id="BizShortCutsTools" Name="Deployment Tools" />
    </Directory>
  </Directory>
  <?endif?>
  <Directory Id="ProgramFilesFolder" Name="ProgramFiles">
    <Directory Id="ProductDir" Name="$(var.ProductName)">
      <Directory Id="INSTALLDIR" Name="$(var.ProjectVersion)"/>
    </Directory>
  </Directory>
</Directory>

Edit 20180129 Note that this problem occurs in a server environment, with restricted security for my logged in user. We are permitted to run msi installers (right click, custom option 'Run as [authorized user name]', with the msi UI.

In order to accomplish this via command line, I've launched as PS terminal under that other account, which works up until the point where I add the INSTALLDIR parameter. Then it simply displays msiexec help.

I doubt it makes a difference, but local version of msiexec (which works) is 5.0.7601.23593, and serverside (which doesn't work) is 5.0.9600.18333 (i.e. more recent).

Are you sure you are setting the INSTALLDIR property properly in your command line? What is your msiexec.exe command line? When you set a property with spaces in the value you must use quotes around the value; INSTALLDIR="E:\Product Name\Install Folder" — Brian Sutherland
– Brian Sutherland, Commented Jan 26, 2018 at 16:58
So, this works on my local dev, but not on our test server. The main differences between these machines is that the local machine doesn't run a server OS, is more restrained in security policies (obviously), and that I need to run msiexec as a different user than the logged in user. But if security would be a problem, I would expect an error message with that kind of feedback, rather than popping up the help box, but perhaps that's simply how msiexec works? — cordifed
– cordifed, Commented Jan 29, 2018 at 10:11

Thomas F. Abraham · Accepted Answer · 2018-01-28 05:59:46Z

0

First, upgrade to the Deployment Framework for BizTalk v5.6 or newer.

Second, in your .btdfproj, add DefaultInstallDir:

<PropertyGroup>
  <!-- existing MSI properties -->
  <ProductUpgradeCode>GUID-HERE</ProductUpgradeCode>
  <!-- add DefaultInstallDir -->
  <DefaultInstallDir>E:\MyCustomPath</DefaultInstallDir>
</PropertyGroup>

The MSI will now default to E:\MyCustomPath.

answered Jan 28, 2018 at 5:59

Thomas F. Abraham

2,1721 gold badge19 silver badges24 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

cordifed Over a year ago

Thanks, this is a great option to resolve the issue, although I'm still curious for the cause/resolution for the msiexec INSTALLDIR parameter issue.

cordifed Over a year ago

I did find that when you use the DefaultInstallDir option to another drive, and that drive doesn't exist on the target machine, msiexec fails with a message 'The folder path [...] contains an invalid character'. Although this is somewhat annoying, it unintentionally prevents anyone from installing a BizTalk application onto a machine that's not supposed to run it, since local workstations typically don't have an E:-drive.

Collectives™ on Stack Overflow

Deploy BizTalk application msi (created with BTDF) via msiexec

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related