Import WindowsPhoneDriver as Winium.Silverlight#164
Conversation
.Winium.StoreApps.ConnectionInformation.json -> .Winium.Mobile.ConnectionInformation.json
NickAb
left a comment
There was a problem hiding this comment.
Skimmed over the changes. I'll try to take deeper look at this one as soon as on Friday.
| #region Public Properties | ||
|
|
||
| public const string FileName = ".Winium.StoreApps.ConnectionInformation.json"; | ||
| public const string FileName = ".Winium.Mobile.ConnectionInformation.json"; |
There was a problem hiding this comment.
I think we should look into backwards compatibility and support both names for a couple of releases. If new file is not found, then it should fallback to the old one and log warning message.
There was a problem hiding this comment.
I wouldn't say that this is backwards compatibility issue. Public API wasn't changed. Do we support work for different driver/server versions?
Will have a look at this case later.
There was a problem hiding this comment.
I will take a look at this myself. It would be nice to have a gradual transition if it easy to implement. Else we should include some useful message if not connection file was found, so it would be easy to pinpoint the problem of incompatible driver and inner server by end user, who might have messed with versions of inner and outer parts.
| <Import Project="$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props" Condition="Exists('$(MSBuildExtensionsPath)\$(MSBuildToolsVersion)\Microsoft.Common.props')" /> | ||
| <PropertyGroup> | ||
| <MinimumVisualStudioVersion>12.0</MinimumVisualStudioVersion> | ||
| <MinimumVisualStudioVersion>11.0</MinimumVisualStudioVersion> |
There was a problem hiding this comment.
Why visual studio version has been downgraded? What version of VS did you use to make changes?
There was a problem hiding this comment.
Have no idea why VS has decided to downgrade it. It happened when I added target for WP Silverlight 8.1
I use VS Enterprise 2015 (14.0.25431.01 Update 3).
| <TargetFrameworkProfile>Profile151</TargetFrameworkProfile> | ||
| <TargetFrameworkVersion>v4.6</TargetFrameworkVersion> | ||
| <TargetFrameworkProfile>Profile259</TargetFrameworkProfile> | ||
| <TargetFrameworkVersion>v4.5</TargetFrameworkVersion> |
There was a problem hiding this comment.
Is it because of Silverlight support?
There was a problem hiding this comment.
Could you please try to add target for Silverlight by yourself (you need to replace 89035d8 commit)
| this.PingTimeout = DefaultPingTimeout; | ||
| this.NoFallback = true; | ||
| this.CommandSettings = new CommandSettings(); | ||
| this.IsJavascriptEnabled = true; |
There was a problem hiding this comment.
Is it required to call ExecuteScript in some selenium bindings? In python selenium bindings do not check this flag at all and allow calling ExecuteScript commands anyway.
It is minor, but will be nice to check this, because it implies javascript support, not some custom "scripting" support.
There was a problem hiding this comment.
Ruby client checks that javascript enabled before executing script.
https://github.com/SeleniumHQ/selenium/blob/650a1ab4fe3f0363cde72d8e0202e61e3f713acd/rb/lib/selenium/webdriver/remote/bridge.rb#L620
Winium/Winium.sln
Outdated
| EndGlobalSection | ||
| GlobalSection(SolutionConfigurationPlatforms) = preSolution | ||
| Debug|Any CPU = Debug|Any CPU | ||
| Debug|ARM = Debug|ARM |
There was a problem hiding this comment.
I don't think we need that much configurations. Visual Studio creates them automatically when any project is added. Need to investigate if that can be prevented in future. Meanwhile, simple deletion of unnecessary configurations will suffice.
There was a problem hiding this comment.
I don't mind to remove it, but why do we care about it?
There was a problem hiding this comment.
When building Debug or Release configuration it will build for all platforms (x86, arm, anycpu), which is redundant in our case. You will also have to maintain these configuration when adding new projects, etc, because sometime VS does not add new projects to each configuration correctly.
The icing on the cake!
|
@NickAb ok, it seems it's ready 🎆 |
|
@bayandin Thanks, merged 👍 |

PrepareRelease.ps1)