The Deployment Framework for BizTalk is the most powerful and customizable, yet easy-to-use toolkit for deploying and configuring your BizTalk solutions.
This makes a difference in terms of when this variable can be used. Now it is not set until the Bootstrap target is run. So, if you use this variable before that (e.g. to define the config file for your BizTalk Application):
it makes the ConfigurationFilePath default to simply \EnterpriseLibrary.config
This makes the DeployBtsNtSvcExeConfig target to fail during the deployment as it cannot find the C:\EnterpriseLibrary.config file
I fixed the problem on our end by redefining the following Item Group as:
In the latest version of the BTDF (5.6) the MSBuildProjectDirectoryParent variable is set in the Bootstrap target.
In the previous versions it was set as part of the property group:
This makes a difference in terms of when this variable can be used. Now it is not set until the Bootstrap target is run. So, if you use this variable before that (e.g. to define the config file for your BizTalk Application):
it makes the ConfigurationFilePath default to simply \EnterpriseLibrary.config This makes the DeployBtsNtSvcExeConfig target to fail during the deployment as it cannot find the C:\EnterpriseLibrary.config file
I fixed the problem on our end by redefining the following Item Group as:
I am not sure how many people ran into the same issue and what would be the proper fix in BTDF, but I thought I would share the finding.
Thanks! Dima M.
This work item was migrated from CodePlex
CodePlex work item ID: '11071' Vote count: '1'