[TIMOB-20096] Windows: Support deploying to Win 10 devices using WinAppDeployCmd
| GitHub Issue | n/a |
|---|---|
| Type | Improvement |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2016-02-11T14:32:39.000+0000 |
| Affected Version/s | Release 5.2.0 |
| Fix Version/s | Release 5.3.0, windowslib 0.4.0 |
| Components | Windows |
| Labels | n/a |
| Reporter | Christopher Williams |
| Assignee | Christopher Williams |
| Created | 2015-12-03T14:23:08.000+0000 |
| Updated | 2016-05-23T19:14:37.000+0000 |
Description
There's a new command line deployment tool for Windows 10, WinAppDeployCmd. It doesn't list the emulators at all, and does an async search on the network for devices. We can use it to list, update, install and uninstall apps on devices (connected via USB or on the same subnet), but it uses different args/switches than the legacy AppDeployCmd/XapDeployTool.
It also may require inputting a pin from the device to connect and do it's work.
From my testing it seems you don't need a PIN to install an application to a Windows 10 device.
WinAppDeployCmd install -f <appx> -g <DeviceGUID>To launch applications the 8.1AppDeployCmdcan still be used.AppDeployCmd /launch <app-id> /targetdevice:<DeviceIndex>Verified using: Windows 10 Pro Visual Studio 2015 Community Update 2 Appc Core: 5.3.0-46 Appc NPM: 4.2.5-5 Ti SDK: 5.3.0.v20160523083840 Lumia 930 W10M Building to a Windows 10 mobile device can now be done through Studio and CLI. Closing ticket