Open tfabraham opened 6 years ago
[BizTalkers@10/14/2015] Hi Lex, I use the powershell script UpdateVersionInfo.ps1 to achieve this. It is described on the following link, look for the heading "Track Your Builds" [https://biztalkalm.codeplex.com/wikipage?title=Build%20and%20deploy%20multiple%20BizTalk%20applications&referringTitle=Build%20with%20dependent%20BizTalk%20applications](biztalk alm) Regards, Rob.
Hi,
At a customer we are rewriting custom MSBuilds-targets (which were executed by BTDF), to automatically increase the Build version of the MSI, the Build version in the Deployment project and in the check in comment. Therefore, someone else, wrote custom MSBuild targets, which checked out the Deployment project, increased the Build version in the Deployment project and checked in the Deployment project.
This worked perfectly fine with BizTalk 2006 and Deployment Framework 3. Each time a MSI was generated, the Deployment project and the checkin comment were all provided with the increased version number.
Nowadays we work wth BizTalk 2013 R2 and BTDF 6 and we want to use the same targets again. After we had built in those targets, it seemed that during the generation of the MSI, the Build version was increased in the Deployment project and the check in comment, but not in the MSI. After checking the output of the generation of the MSI I assume that, during the generation of the MSI, a script (batch file) becomes generated, which contains the still valid Build version. But that Build version becomes increased by one of the custom MSBuild targets. As a result the Deployment project and the check in comment are provided with the increased Build version, but not the MSI.
Does anyone has experience with increasing the Build version by BTDF? Does someone recognize the mentioned behaviour of BizTalk 2013 R2/BTDF versus BizTalk 2006/BTDF 3?
Looking forward to hear from you!
Best regards, Lex Hegt
This work item was migrated from CodePlex
CodePlex work item ID: '11018' Vote count: '1'