Hi,
I was asked to describe the changes I had to make. I'll try to list them briefly.
1) Use a custom wxs file, which is a copy of \Deployment Framework for BizTalk 5.6\Developer\GenericBizTalkMSI.wxs with the following changes.
Then the btdf project file, should be modified to refer to the custom file by adding the following line, to the first PropertyGroup.
• SSOSettingsEditor.exe
• SSOSettingsFileImport.exe
• SSOSettingsFileReader.dll
The new files , need to replace the ones originally installed with BTDF 5.6, in the following folder: C:\Program Files (x86)\Deployment Framework for BizTalk 5.6\Framework\DeployTools
SSOSettingsFileReader.dll should also be added to the Global Assembly Cache (GAC).
3) For some reason, when installing BTDF on a machine with BizTalk 2016, it gets the version of gacutil wrong, so it copies the 2.0 version to the DeployTools folder, and also does not copy it’s dependencies as they are unneeded.
The solution is to copy the 4.0 version of the following 3 files into the DeployTools folder of BTDF.
• Gacutil.exe
• Gacutil.exe.config
• Gacutlrc.dll
4) Any files that should be added to the Global Assembly Cache during the BTDF installation, seem to not be added, due to the issue discussed above. For that reason, the following two files need to be added to the GAC manually.
• log4net.dll
• log4net.Ext.Serializable.dll
5) the VS Addin won't work, so you have to build and do all BTDF actions using the command line. All explained in the documentation.
I was asked to describe the changes I had to make. I'll try to list them briefly.
1) Use a custom wxs file, which is a copy of \Deployment Framework for BizTalk 5.6\Developer\GenericBizTalkMSI.wxs with the following changes.
<SetProperty Id="MSBUILDPATH" Action="SetMSBUILDPATH2010" Value="[NETFRAMEWORK40FULLINSTALLROOTDIR]\MSBuild.exe" Sequence="both" After="CostFinalize">
<![CDATA[BTS_PRODUCTNAME = "Microsoft BizTalk Server 2010" OR BTS_PRODUCTNAME = "Microsoft BizTalk Server 2013" OR BTS_PRODUCTNAME = "Microsoft BizTalk Server 2013 R2" OR BTS_PRODUCTNAME = "Microsoft BizTalk Server 2016"]]>
</SetProperty>
<SetProperty Id="MSBUILDTOOLSVER" Action="SetMSBUILDTOOLSVER2010" Value="/tv:4.0" Sequence="both" After="SetMSBUILDPATH2010">
<![CDATA[BTS_PRODUCTNAME = "Microsoft BizTalk Server 2010" OR BTS_PRODUCTNAME = "Microsoft BizTalk Server 2013" OR BTS_PRODUCTNAME = "Microsoft BizTalk Server 2013 R2" OR BTS_PRODUCTNAME = "Microsoft BizTalk Server 2016"]]>
</SetProperty>
Then the btdf project file, should be modified to refer to the custom file by adding the following line, to the first PropertyGroup.
<!-- Use the custom WXS file which enables BizTalk 2016-->
<WixProjectFile>BizTalk2016MSI.wxs</WixProjectFile>• SSOSettingsEditor.exe
• SSOSettingsFileImport.exe
• SSOSettingsFileReader.dll
The new files , need to replace the ones originally installed with BTDF 5.6, in the following folder: C:\Program Files (x86)\Deployment Framework for BizTalk 5.6\Framework\DeployTools
SSOSettingsFileReader.dll should also be added to the Global Assembly Cache (GAC).
3) For some reason, when installing BTDF on a machine with BizTalk 2016, it gets the version of gacutil wrong, so it copies the 2.0 version to the DeployTools folder, and also does not copy it’s dependencies as they are unneeded.
The solution is to copy the 4.0 version of the following 3 files into the DeployTools folder of BTDF.
• Gacutil.exe
• Gacutil.exe.config
• Gacutlrc.dll
4) Any files that should be added to the Global Assembly Cache during the BTDF installation, seem to not be added, due to the issue discussed above. For that reason, the following two files need to be added to the GAC manually.
• log4net.dll
• log4net.Ext.Serializable.dll
5) the VS Addin won't work, so you have to build and do all BTDF actions using the command line. All explained in the documentation.