自动化解决方案正在正确清洁和构建,但是在使用构建定义进行构建时,其抛出错误,
它会检查我们要保存生成的解决方案.dll文件并抛出错误的位置上的文件:
Desktop \ Pages \ NewFieldPropertiesPage.cs(729,45):错误CS1705:程序集'Aptean.Windows.Automation'的标识为'Aptean.Windows.Automation,Version = 1.0.0.0,Culture = neutral,PublicKeyToken = null'使用“ UiaComWrapper,版本= 14.0.0.0,文化=中性,PublicKeyToken = b03f5f7f11d50a3a”,其版本高于引用的程序集“ UiaComWrapper”,标识为“ UiaComWrapper,版本= 12.0.0.0,文化=中性,PublicKeyToken = b03f5f7f11d50a3a” [C :\ agent-DGA1BDT04TFS13_work \ 1 \ s \ Respond.Test.Base \ Respond.Test.Base.csproj]
这是我们定义自动化元素的方式: 并在来自“ System.Windows.Automation”程序集的“ AutomationElement”和“ PropertyCondition”中找到错误
``` {
``` get
``` {
``` AutomationElement root = AutomationElement.RootElement;
``` PropertyCondition PropApplicaionRoot = new PropertyCondition(AutomationElement.AutomationIdProperty, "MainForm");
``` AutomationElement ApplicationRoot = root.FindFirst(TreeScope.Subtree, PropApplicaionRoot);
``` PropertyCondition PropSideMenuRoot = new PropertyCondition(AutomationElement.AutomationIdProperty, "pnlObjectAndFieldDetails");
``` AutomationElement SideMenuRoot = ApplicationRoot.FindFirst(TreeScope.Subtree, PropSideMenuRoot);
``` PropertyCondition propEntitiesAndFields = new PropertyCondition(AutomationElement.NameProperty, "Boolean Field 135374");
``` AutomationElement OKButton = SideMenuRoot.FindFirst(TreeScope.Subtree, propEntitiesAndFields);
``` return OKButton;
``` }
``` }
Below is the error i am getting, one of the error statement:
Respond.Test.Base\Desktop\UIMap\SelectSkillPageMap.cs (30, 45)
Respond.Test.Base\Desktop\UIMap\SelectSkillPageMap.cs(30,45): Error CS1705: Assembly 'Aptean.Windows.Automation' with identity 'Aptean.Windows.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' uses 'UiaComWrapper, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' which has a higher version than referenced assembly 'UiaComWrapper' with identity 'UiaComWrapper, Version=12.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
答案 0 :(得分:0)
实际上,我们正在检入正确的文件,并且还在构建解决方案,同时深入挖掘提到的错误, 仅当在VM中使用源解决方案进行构建时,它才失败,而在最新情况下并没有更改参考文件。 从该位置删除了解决方案,然后运行VNext构建已解决了该问题,因为这一次它从源中获取了最新版本的.dll文件。
谢谢。