-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
.NET developers can run iOS and Android apps on emulators and devices in .NET 6 #44654
Comments
@marek-safar not sure if you want to move this to the mono repo? |
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label. |
after reviewing with the Xamarin Tools team, we do not think there is much here from the perspective of the IDEs. Please let us know if otherwise. This assumes that the IDEs will continue to install the emulators. Should .NET consider installing the emulators such that they can be available for .NET CLI scenarios? |
What about Visual Studio Code? |
As is possible with React Native and Flutter, .NET developers should be able to call an emulator through the CLI, preferably with the |
We already have a |
As specified in dotnet#44654 the minimum iOS/tvOS version we're targeting for .NET 6 is iOS 10. Bump the versions used in our build scripts and RID graph to that and also add iOS 14.
As specified in #44654 the minimum iOS/tvOS version we're targeting for .NET 6 is iOS 10. Bump the versions used in our build scripts and RID graph to that and also add iOS 14.
Tagging subscribers to 'arch-android': @steveisok, @akoeplinger Issue DetailsAs part of One .NET effort, we are building support for existing Xamarin workloads to be migrated to dotnet/runtime platform. To make this successful there are several components which will need to be updated or re-build for native support of Xamarin as optional workloads in .NET. Work ItemsShared
iOS/tvOS
Oldest supported versions: iOS 10, tvOS 10 Android
Oldest supported version: API 21
|
@steveisok is there any 6.0 work left here? If not we can close it and copy anything we want to keep into a 7.0 one. |
This story spans a couple of teams. There is some activity with respect to the tests going on. @SamMonoRT anything from your end? |
We have a few runtime tests running on Android devices/simulators in the CI lanes. For iOS, we are just wrapping up a couple PRs to gets some tests running on devices. I believe at this time, we are confident this scenario of running iOS and Android apps on devices/simulators/emulators in .NET6 is satisfied, and we can move this to 7.0 (or as Dan mentions, copy over remaining work to a new 7.0 issue) |
@jamshedd is it ok to change the milestone on a partially completed story or is it important we create a new one and copy the remainder over? I assume the former. |
Moving is fine. I did happen to notice the User Story shows "Committed", this should be "In Progress" I think? |
As part of One .NET effort, we are building support for existing Xamarin workloads to be migrated to dotnet/runtime platform. To make this successful there are several components which will need to be updated or re-build for native support of Xamarin as optional workloads in .NET.
Work Items
Shared
iOS/tvOS
ios-arm64
,ios-arm32
,ios-x64
runtime packsOldest supported versions: iOS 10, tvOS 10
Android
android-arm64
,android-arm32
,android-x64
runtime packsOldest supported version: API 21
The text was updated successfully, but these errors were encountered: