The Deployment Framework for BizTalk is the most powerful and customizable, yet easy-to-use toolkit for deploying and configuring your BizTalk solutions.
MIT License
53
stars
24
forks
source link
*Qualified ItemGroups should be computed inside their respective deployment Targets or the Targets should depend on the *Qualified ItemGroups only #362
If the *Qualified ItemGroups (Schemas, Transforms, FilesToXmlPreprocess, ...) were computed inside they respective deployment targets, one could inject items in the non-qualified ItemGroups from a custom target that runs before the one that actually deploys the items.
For instance, depending on some param, I need to add FilesToXmlPreprocess items, but I can only do this inside a Target (due to the way MSBuild work a.o.). Because I also depend on the many things BTDF provide and setup, I can only declare my target after having imported BTDF file. But, it is too late for the FilesToXmlPreprocessQualified ItemGroup to take my item when being computed.
However I know my custom target runs before the PreprocessFiles target. What allows me to add it myself to the FilesToXmlPreprocessQualified ItemGroup. But because the PreprocessFiles target also has condition on FilesToXmlPreprocess ItemGroup I also need to add my item in this ItemGroup should it be the only file to preprocess...
I would be simpler if
either one could simply add an item to the regular ItemGroups (i.e. the non Qualified ones) and have the Qualified ones be computed inside their respective deployment targets,
or the deployment targets would only depend on the *Qualified ItemGroups and not the regular ones. For instance <Target Name="PreprocessFiles" Condition="'@(FilesToXmlPreprocessQualified)' != '' ... and not Condition="'@(FilesToXmlPreprocess)' != '' ...
If the *Qualified ItemGroups (Schemas, Transforms, FilesToXmlPreprocess, ...) were computed inside they respective deployment targets, one could inject items in the non-qualified ItemGroups from a custom target that runs before the one that actually deploys the items.
For instance, depending on some param, I need to add FilesToXmlPreprocess items, but I can only do this inside a Target (due to the way MSBuild work a.o.). Because I also depend on the many things BTDF provide and setup, I can only declare my target after having imported BTDF file. But, it is too late for the FilesToXmlPreprocessQualified ItemGroup to take my item when being computed.
However I know my custom target runs before the PreprocessFiles target. What allows me to add it myself to the FilesToXmlPreprocessQualified ItemGroup. But because the PreprocessFiles target also has condition on FilesToXmlPreprocess ItemGroup I also need to add my item in this ItemGroup should it be the only file to preprocess...
I would be simpler if
either one could simply add an item to the regular ItemGroups (i.e. the non Qualified ones) and have the Qualified ones be computed inside their respective deployment targets,
or the deployment targets would only depend on the *Qualified ItemGroups and not the regular ones. For instance <Target Name="PreprocessFiles" Condition="'@(FilesToXmlPreprocessQualified)' != '' ... and not Condition="'@(FilesToXmlPreprocess)' != '' ...
Thanks François
This work item was migrated from CodePlex
CodePlex work item ID: '10778' Vote count: '1'