Objective
Source Location
Modifications
Developer Scripts
My objective was to modify BizTalk Deployment framework source, with the intend of getting it to work with BizTalk 2016, as it does not work out of the box with BizTalk 2016.
BizTalk Deployment Framework source is located at CodePlex and downloaded from below link
It has BTDF 6.0 under dev folder and BTDF 5.0- 5.6 under release folder.
BTDF 5.6 release version is more suited, as it is a stable release, hence it is modified to suit our need. All the references going forth are from the 5.6 release folder.
Below is the modification that were done in order to get BTDF 5.6 release version, working.
1. Added copy of BizTalk 2016 SSOClient to \Tools\SSOSettingsFileImport\ExternalReferences\BTS2016\Microsoft.BizTalk.Interop.SSOClient.dll, we will use as reference later.
2. In solution, \Tools\SSOSettingsFileImport\SSOSettingsFileImport.sln clone projects SSOSettingsEditorBTS2013R2, SSOSettingsFileImportBTS2013R2 and SSOSettingsFileReaderBTS2013R2 projects, rename then as BTS2016 as shown below,
a. SSOSettingsEditorBTS2016
b. SSOSettingsFileImportBTS2016
c. SSOSettingsFileReaderBTS2016
For the above projects change target .net framework to 4.6, add reference to SSOClient.dll and in post build make appropriate changes
3. In solution, \Installer\BizTalkDeploymentFrameworkInstaller.sln, change RuntimeComponents.wxi by adding reference to BizTalk 2016 and added step to GAC SSOFileReader dll, apart from being coped to installation folder, for reference your reference the file @ link,
4. In wix file located at Developer\GenericBizTalkMSI.wxs, add reference to BizTalk 2016, for your reference check file @ link,
The resulting MSI after the fix is loaded @ link
As BTDF Visual Studio add-in is not compatible with Visual Studio 2015, use below command to execute the reqired task instead,
Note: There are two set of command but the variation is for configuration variation of the project
Quick Deploy
MSBuild.exe <btdfproj file path> /nologo /p:Configuration=Debug /t:UpdateOrchestration
MSBuild.exe <btdfproj file path> /nologo /p:Configuration=Release /t:UpdateOrchestration
Update SSO
MSBuild.exe <btdfproj file path> /nologo /p:Configuration=Debug /t:DeploySSO
MSBuild.exe <btdfproj file path> /nologo /p:Configuration=Release /t:DeploySSO
Preprocess Bindings
MSBuild.exe <btdfproj file path> /nologo /p:Configuration=Debug /t:PreprocessBindings
MSBuild.exe <btdfproj file path> /nologo /p:Configuration=Release /t:PreprocessBindings
Bounce BizTalk
MSBuild.exe <btdfproj file path> /nologo /t:BounceBizTalk
Import Bindings
MSBuild.exe <btdfproj file path> /nologo /t:ImportBindings /p:Configuration=Debug
MSBuild.exe <btdfproj file path> /nologo /t:ImportBindings /p:Configuration=Release
Export Settings
MSBuild.exe <btdfproj file path> /nologo /t:ExportSettings /p:Configuration=Debug
MSBuild.exe <btdfproj file path> /nologo /t:ExportSettings /p:Configuration=Release
Undeploy Rules
MSBuild.exe <btdfproj file path> /nologo /t:UndeployVocabAndRules /p:Configuration=Debug;RemoveRulePoliciesFromAppOnUndeploy=true
MSBuild.exe <btdfproj file path> /nologo /t:UndeployVocabAndRules /p:Configuration=Release;RemoveRulePoliciesFromAppOnUndeploy=true
Deploy Rules
MSBuild.exe <btdfproj file path> /nologo /t:DeployVocabAndRules /p:Configuration=Debug;ExplicitlyDeployRulePoliciesOnDeploy=true
MSBuild.exe <btdfproj file path> /nologo /t:DeployVocabAndRules /p:Configuration=Release;ExplicitlyDeployRulePoliciesOnDeploy=true
Deploy
MSBuild.exe <btdfproj file path> /nologo /t:Deploy /p:Configuration=Debug
MSBuild.exe <btdfproj file path> /nologo /t:Deploy /p:Configuration=Release
Undeploy
MSBuild.exe <btdfproj file path> /nologo /t:Undeploy /p:Configuration=Debug
MSBuild.exe <btdfproj file path> /nologo /t:Undeploy /p:Configuration=Release
Build MSI
MSBuild.exe <btdfproj file path> /nologo /p:Configuration=Debug /t:Installer
MSBuild.exe <btdfproj file path> /nologo /p:Configuration=Release /t:Installer
This is probably why Netmarble determined to make the transfer fast and purchase the corporate earlier than it’s turn out to be 토토사이트 too large for an acquisition. There aren't any separate change of company management triggers for gaming and gambling firms. As mentioned in 10.1 Disclosure Requirements, general guidelines apply and change of management triggers would include belongings or revenues standards. Obligations beneath the FTRA apply to on line casino operators, as well as|in addition to} monetary establishments, digital monetary business operators and certain loan business operators.
ReplyDelete