Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add support for Visual Studio Android Emulator
See original GitHub issueSince there is already support for third party Android emulators (Genymotion) could you also add support for Microsoft’s one.
It is a viable option when developing on a Windows machine since it is a way snappier than the stock Android emulator and has functionallity which is available only in the paid version of Genymotion. Even if users do not have Visual Studio 2015 on their machines, they can install the emulator separately.
Currently the integration with {N} actually works out of the box - I tried the build, run and livesync commands and they are fine.
What I would like to see is a command which starts the Visual Studio Emulator, something like
$ tns run android --emulator --vs DEVICE_NAME
Also running tns device results in the following:
1: 'undefined' Android 169.254.190.187:5555
The device name should be displayed correctly and maybe an identifier to easily recognize this device as a Visual Studio Emulator.
Issue Analytics
- State:
- Created 8 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@enchev I would like to have this working. With Windows 10 it is a very useful feature, especially if you use docker heavily. Think it could be re-opened but low priority?
tns run android --device 169.254.138.177:5555 and you get the device from:
adb devices enjoy!