Closed ramiabughazaleh closed 8 years ago
I'm still trying to resolve/troubleshoot why the silverlight tests fail for these on the build server. They work on my machine. :grin:
Tell me if you wan't me to help you in any way, run it on my machine or whatever.
Thank you.
I just resolved the build issue, as the last build succeeded, and so this PR is now ready for your review, whenever you have the time.
Thank you! :smile:
The code looks really good, and the build on AppVeyor succeeded. Seems to be a good day for CUITe.
updated build to make ConfigurationName dynamic, default is Release checking for errors on each build step and failing on first error consolidated conflicting values for the VisualStudioVersion property defining conditional compilation symbols based on the VisualStudioVersion property fixed CUITe.Integration.Tests removed references to conditional compilation symbol SILVERLIGHT_SUPPORT added By.ControlType and By.ControlInstance search configurations removed references to Microsoft.VisualStudio.TestTools.UITest.Extension.Silverlight in non-silverlight projects made WebDevServer port dynamic to avoid re-using ports that may already be in use Installing Microsoft Silverlight 5 Developer Runtime for Windows (64 bit) during build using SilverlightUIAutomationHelper.dll version from SilverlightVersion project property automatically limiting searching for silverlight controls by its parent added silverlight child window and corresponding test