On top of the aforementioned warning, I am also getting a few of the following one:
Here are some workable regular expressions they you can add to the Exec tasks. I did this for all the BTDF deploy targets that I am using and that are both relying on BTSTask and exhibiting the symptoms. They do seem to work for me, well at least they discard the annoying warnings:
Maybe you could systematically add them into BTDF? Or better yet, provide some properties that one could chose to overwrite, rather than having to redefine the BTDF targets that are concerned (similarly to the example provided below)!
As a side note, I am now using BTS 2013 R2 and BTDF 6.0, but I was used to BTS 2009 and BTDF 5 RTW. The issues were already present back then, but probably because the Exec MSBuild task worked differently, they were not reported as warnings. To get the exact (or so it seems) same behaviour as with BTS 2009 and BTDF 5, one would not need any regular expression but could simply use the following Exec attribute:
François
EXEC : warning : Assembly "Be.Stateless.BizTalk.Transforms, ..." depends on the following assemblies that must be installed in the Global Assembly Cache for runtime to succeed:
Assembly "Be.Stateless.BizTalk.Schemas, ..."Here are some workable regular expressions they you can add to the Exec tasks. I did this for all the BTDF deploy targets that I am using and that are both relying on BTSTask and exhibiting the symptoms. They do seem to work for me, well at least they discard the annoying warnings:
IgnoreStandardErrorWarningFormat="true"
CustomErrorRegularExpression="^(?i:(?!command succeeded).*(error).+)$"
CustomWarningRegularExpression="^(?i:(?!command succeeded).*(warning)(?!.+(may be necessary to restart the Host Instance|depends on the following assemblies that must be installed)).+)$"Maybe you could systematically add them into BTDF? Or better yet, provide some properties that one could chose to overwrite, rather than having to redefine the BTDF targets that are concerned (similarly to the example provided below)!
As a side note, I am now using BTS 2013 R2 and BTDF 6.0, but I was used to BTS 2009 and BTDF 5 RTW. The issues were already present back then, but probably because the Exec MSBuild task worked differently, they were not reported as warnings. To get the exact (or so it seems) same behaviour as with BTS 2009 and BTDF 5, one would not need any regular expression but could simply use the following Exec attribute:
IgnoreStandardErrorWarningFormat="true"-
Redefine BTDF MSBuild targets as in the following file
BizTalk.Factory.Deployment.IgnoreStandardErrorsAndWarnings.targets -
then define a property, (in my case, defined in the main btdfproj file, see line 85 of BizTalk.Factory.Deployment.btdfproj)
<IgnoreStandardErrorWarningFormat>true</IgnoreStandardErrorWarningFormat>- on the basis of this property, conditionnally import a set of MSBuild targets, just after having imported the regular BTDF targets, (in my case, declared in the custom targets file, see line 72 of BizTalk.Factory.Deployment.targets)
<Import Project="BizTalk.Factory.Deployment.IgnoreStandardErrorsAndWarnings.targets" Condition=" '$(IgnoreStandardErrorWarningFormat)' == 'true' " />François