Thanks for your post,
Those orchrestrations are packaged in multiple assemblies and I don't planned to bump the version number.
I have found one solution to my problem. I don't know if it's the best solution but it works. I explain :
I have modified the deployments file : BizTalkDeploymentFramework.targets in the folder : C:\Program Files (x86)\MSBuild\DeploymentFrameworkForBizTalk\5.0
I have added a new XML configuration tag like this :
<!-- Specific flag -->
<SkipRemoveApp Condition="'$(SkipRemoveApp)' == ''">false</SkipRemoveApp>
I set this flag to true in my .btdfproj file.
In the BizTalkDeploymentFramework.targets file I have used this flag to skip the application remove step during undeployment process.
Every where in the file where it deploy a biztalk item (Schemas, Transform, Orch etc...) I have conditionned the classic BTSTask.exe command line with my flag to do -Overwrite or not.
My only principal problem was : If I don't remove the application, I cannot redeploy the same orchestration because it was not unenlisted. I have solved this problem with a new command line using "StopOrch.vbs" to stop and unenlist each orchestrations decribe
in my .btdfproj file.
I have posted my file on my blog. See the following link to download the modified file :
I m sorry but my blog is in french. You can download my file and do a "windiff" with your file to see de diffrences. Maybe you can tell me what do you think about my method ?