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
Welcome to .NET for Android 10! These release notes are intended to call out user-facing enhancements and changes as we build the next version of .NET for Android.
Note that this document is being built as we commit changes, so it will contain information about previews that may not have been released yet. Also note that the intention of previews is to try out changes and get feedback, so these changes could be removed before the final .NET 10 release.
Please file any feedback about these features as issues in this repository!
Previously we could not support dotnet run for .NET for Android projects because it did not accept parameters needed to specify which Android device or emulator to use.
Now that the .NET SDK team has added this support, .NET for Android projects can be run using dotnet run:
// Run on the only attached Android physical device
dotnet run -p:AdbTarget=-d
// Run on the only running Android emulator
dotnet run -p:AdbTarget=-e
// Run on the specified Android physical device or emulator
dotnet run -p:AdbTarget="-s emulator-5554"
The AdbTarget property is passed to adb. Its specification is documented here.
A new way of creating the marshal methods needed for Java calling into C# code promises to provide startup performance improvements. Unfortunately, we weren't able to get them stabilized in time for .NET 9 and thus .NET 9 shipped with them off by default.
For .NET 10 previews we have re-enabled them by default to continue testing and getting feedback. Problems with these marshal methods often manifest as a hang at startup. If you are getting a hang on startup on .NET 10 previews that you didn't see on .NET 9, try disabling marshal methods. If this fixes the hang, please file an issue letting us know there are still issues with marshal methods.
Add ArtifactFilename metadata for @(AndroidMavenLibrary) item (#9479)
@(AndroidMavenLibrary) was added in .NET 9 and allows a Java library to be automatically downloaded from Maven to be bound. Generally this library is named {artifact.Id}-{artifact.Version}.[jar|aar], however we later found out it does not follow a standard and could be arbitrarily different.
Add the ArtifactFilename metadata to @(AndroidMavenLibrary) to allow an alternative file name:
Welcome to .NET for Android 10! These release notes are intended to call out user-facing enhancements and changes as we build the next version of .NET for Android.
Note that this document is being built as we commit changes, so it will contain information about previews that may not have been released yet. Also note that the intention of previews is to try out changes and get feedback, so these changes could be removed before the final .NET 10 release.
Please file any feedback about these features as issues in this repository!
.NET 10 Preview 1 - Unreleased
Android 16 (Baklava) Developer Preview 1 Bindings (#9594)
Google has released Developer Preview 1 of the Android 16 (API-36) SDK. Support has been adding for using these preview API.
To target the Android 16 preview API:
TargetFramework
tonet10.0-android36
Support for
dotnet run
(#9470)Previously we could not support
dotnet run
for .NET for Android projects because it did not accept parameters needed to specify which Android device or emulator to use.Now that the .NET SDK team has added this support, .NET for Android projects can be run using
dotnet run
:The
AdbTarget
property is passed toadb
. Its specification is documented here.Enable Marshal Methods by Default (#9551)
A new way of creating the marshal methods needed for Java calling into C# code promises to provide startup performance improvements. Unfortunately, we weren't able to get them stabilized in time for .NET 9 and thus .NET 9 shipped with them off by default.
For .NET 10 previews we have re-enabled them by default to continue testing and getting feedback. Problems with these marshal methods often manifest as a hang at startup. If you are getting a hang on startup on .NET 10 previews that you didn't see on .NET 9, try disabling marshal methods. If this fixes the hang, please file an issue letting us know there are still issues with marshal methods.
Add
ArtifactFilename
metadata for@(AndroidMavenLibrary)
item (#9479)@(AndroidMavenLibrary)
was added in .NET 9 and allows a Java library to be automatically downloaded from Maven to be bound. Generally this library is named{artifact.Id}-{artifact.Version}.[jar|aar]
, however we later found out it does not follow a standard and could be arbitrarily different.Add the
ArtifactFilename
metadata to@(AndroidMavenLibrary)
to allow an alternative file name:The text was updated successfully, but these errors were encountered: