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
We have a requirement to test the integration of the ICorDebug Debugger and the .NET Android Sdk.
In order to meet this requirement, we need to be able to build .NET Android applications on the Helix bots themselves.
This is because some of the debug scenarios use tooling which is part of the build system. For example we would need to be able to run commands such as
Currently the Helix bots only include adb and emulator tooling. While those do allow us to install a full apk, it does not allow us to test the specific debugging path which side-loads assemblies.
Ideally we would like to be able to test this on Windows, Mac and Linux since those are all the platforms our customers use.
However I am aware that running the Android emulators on Windows can be problematic.
The planned release of the ICorDebug integration/switch is VS 17.14. Which I guess is scheduled for //build which is in May 2025.
The text was updated successfully, but these errors were encountered:
We have a requirement to test the integration of the ICorDebug Debugger and the .NET Android Sdk.
In order to meet this requirement, we need to be able to build .NET Android applications on the Helix bots themselves.
This is because some of the debug scenarios use tooling which is part of the build system. For example we would need to be able to run commands such as
Currently the Helix bots only include
adb
andemulator
tooling. While those do allow us to install a full apk, it does not allow us to test the specific debugging path which side-loads assemblies.Ideally we would like to be able to test this on Windows, Mac and Linux since those are all the platforms our customers use.
However I am aware that running the Android emulators on Windows can be problematic.
The planned release of the ICorDebug integration/switch is VS 17.14. Which I guess is scheduled for //build which is in May 2025.
The text was updated successfully, but these errors were encountered: