Hi Nikhil,
There was a previous discussion along the same lines. It is not built-in functionality.
Will you have the other SettingsFileGenerator.xml file when you build the MSI, or will it exist only on the server and completely separate from your app deploy?
If it is completely separate, then you'd have to make an assumption of where it is located on the server and code your .btdfproj changes to use that location. You can add a Target element in your .btdfproj with the AfterTargets="ExportSettings" attribute, which will run immediately after your app's settings export. In there, you can call EnvironmentSettingsExporter.exe to export the other file. As for the bindings file, XmlPreprocess.exe itself supports multiple settings XML files with multiple /s parameters, but the Deployment Framework is coded to use only one file and one parameter.
You could override the PreprocessBindings target in your .btdfproj to add the additional /s parameter. You'd have to copy the PreprocessBindings target from BizTalkDeploymentFramework.targets (in the Program Files\MSBuild folder tree) and paste it into your .btdfproj, then modify it.
Anything is possible since you have the flexibility of MSBuild, but it will take some work on your part to make it come together.
Another option is to build the source code from the Environment Settings Manager, which has an option to merge together multiple setting spreadsheet files. It is unreleased but probably works fine.
Thanks,
Tom
There was a previous discussion along the same lines. It is not built-in functionality.
Will you have the other SettingsFileGenerator.xml file when you build the MSI, or will it exist only on the server and completely separate from your app deploy?
If it is completely separate, then you'd have to make an assumption of where it is located on the server and code your .btdfproj changes to use that location. You can add a Target element in your .btdfproj with the AfterTargets="ExportSettings" attribute, which will run immediately after your app's settings export. In there, you can call EnvironmentSettingsExporter.exe to export the other file. As for the bindings file, XmlPreprocess.exe itself supports multiple settings XML files with multiple /s parameters, but the Deployment Framework is coded to use only one file and one parameter.
You could override the PreprocessBindings target in your .btdfproj to add the additional /s parameter. You'd have to copy the PreprocessBindings target from BizTalkDeploymentFramework.targets (in the Program Files\MSBuild folder tree) and paste it into your .btdfproj, then modify it.
Anything is possible since you have the flexibility of MSBuild, but it will take some work on your part to make it come together.
Another option is to build the source code from the Environment Settings Manager, which has an option to merge together multiple setting spreadsheet files. It is unreleased but probably works fine.
Thanks,
Tom