Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

0.2.0 Support enumerating, launching, installing to Windows 10 Mobile Emulators #27

Merged
merged 3 commits into from Dec 11, 2015

Conversation

sgtcoolguy
Copy link
Contributor

This is a major overhaul of windowslib to better support Windows 10. We now brought back our own custom wptool written in C# that we compile on-demand on the user's system. This tool fills in the gaps from Windows 10 tooling, namely that we can enumerate emulators (without hacking the 8.1 tooling), we can launch/connect to an emulator and grab it's IP address (it launches the emulator to connect to it), and then we can use that info to install/update/uninstall apps on the emulator using the WinAppCeployCmd.exe that MS provides. Additionally our custom tool allows you to launch an app by it's product id (guid). We have a powershell script to grab that out of an appx file so we can just take the built appx as input to install and then launch it.

You can run the included npm tests to exercise some of this (the device ones will likely fail).

Ideally this PR should be tested by basically placing this version of windowslib into a build of the SDK from master and then trying to build for Win 10 emulator and seeing if it works. It's possible it may fail due to other bugs we need to address though.

string command = null;
string wpsdk = null;
string udid = null;
string appid = null;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The indention in this file is pretty bad. Could you please do a quick scrub to ensure everything lines up? Thank you!

@infosia
Copy link
Contributor

infosia commented Dec 11, 2015

Wow awesome, running test-emulator and test-device went through well for Windows 10 Mobile! I saw test-device actually installs TestApp on my usb-connected Windows 10 Mobile phone. 👍 ✨ I also did quick smoke-test on latest titanium_mobile_windows on both Windows 8.1 & 10, and got no regression for Windows Store 8.1 app as well as phone 8.1 app project.

One issue I had is that when I run tests on Windows 8.1, test-emulator failed. It's because there's some Windows 10-specific constants defined (WIN_10, WIN_10_PROJECT etc) and it fails to compile windows 10 project.

Can we use 8.1 sdk when unit tests are running on Windows 8.1? I see no good variable for Windows 8.1 on Node.js OS API though.

Other than that, I think it's good to go. Feel free to merge & bump up package. Nice work!

@infosia
Copy link
Contributor

infosia commented Dec 11, 2015

Ideally this PR should be tested by basically placing this version of windowslib into a build of the SDK from master and then trying to build for Win 10 emulator and seeing if it works. It's possible it may fail due to other bugs we need to address though.

I tried --wp-sdk=10.0 but it says it doesn't support 10.0.

> ti build --platform windows --target wp-emulator --device-id 8-1-6 --win-publisher-id 13AFB724-65F2-4F30-8994-C79399EDBD80 --wp-sdk 10.0
[ERROR] Invalid "--wp-sdk" value "10.0"

Please select a valid wp-sdk value:
 1)  8.0
 2)  8.1

sgtcoolguy added a commit that referenced this pull request Dec 11, 2015
0.2.0 Support enumerating, launching, installing to Windows 10 Mobile Emulators
@sgtcoolguy sgtcoolguy merged commit 76918ea into appcelerator-archive:master Dec 11, 2015
@sgtcoolguy sgtcoolguy deleted the wptool branch December 11, 2015 16:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants