You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2021. It is now read-only.
For now debugger support only one attached device, because it's default behavior of adb: if one attached device all commands directs to it.
adb is used inside Install msbuild task, and device id could be passed via parameter, don't remember exact names, but it is.
Debugger also use adb to setup port forwarding, stop and launch application.
Need to add ability to choose device where to install and debug application.
How it should looks like? It depends on technical ability,
The best option is to implement like in visual studio: picker with running devices.
If it not possible at least it could be done via text config with device id.
The text was updated successfully, but these errors were encountered:
For now debugger support only one attached device, because it's default behavior of
adb
: if one attached device all commands directs to it.adb
is used insideInstall
msbuild task, and device id could be passed via parameter, don't remember exact names, but it is.Debugger also use
adb
to setup port forwarding, stop and launch application.Need to add ability to choose device where to install and debug application.
How it should looks like? It depends on technical ability,
The best option is to implement like in visual studio: picker with running devices.
If it not possible at least it could be done via text config with device id.
The text was updated successfully, but these errors were encountered: