Download .NET 8 RC1<\/a> for Linux, macOS, and Windows.<\/p>\n There are several exciting posts you should check out as well:<\/p>\n https:\/\/github.com\/dotnet\/runtime\/pull\/89258<\/p>\n RC1 sees the inclusion of IAsyncEnumerable streaming deserialization extension methods:<\/p>\n Credit to @IEvangelist for contributing the implementation.<\/p>\n https:\/\/github.com\/dotnet\/runtime\/pull\/89614<\/p>\n It is now possible to create Credit to @brantburnett for contributing the implementation.<\/p>\n https:\/\/github.com\/dotnet\/runtime\/pull\/90006<\/p>\n Adds support for parsing Credit to @DoctorKrolic for contributing the implementation.<\/p>\n https:\/\/github.com\/dotnet\/runtime\/pull\/90013<\/p>\n The existing parameterless Calling the new overload with<\/p>\n will populate the options instance with the default reflection resolver if one is missing. This emulates the initialisation logic employed by the https:\/\/github.com\/xamarin\/xamarin-android\/pull\/8172<\/p>\n We try to choose the best the default configuration for .NET and .NET MAUI applications out of the box. In .NET 6 and higher, specifically, these applications now utilize profiled ahead-of-time (AOT) compilation mode by default when they are built in If performance is more of a concern for your Android application than app size, AOT-compiling all code is a great way to achieve the best startup and runtime performance. Set the following MsBuild property for your Android app:<\/p>\n By default setting \n
\n
System.Text.Json Improvements<\/h2>\n
System.Net.Http.Json<\/code> extensions for IAsyncEnumerable<\/h3>\nconst string RequestUri = \"https:\/\/api.contoso.com\/books\";\r\nusing var client = new HttpClient();\r\nIAsyncEnumerable<Book> books = client.GetFromJsonAsAsyncEnumerable<Book>(RequestUri);\r\n\r\nawait foreach (Book book in books)\r\n{\r\n Console.WriteLine($\"Read book '{book.title}'\");\r\n}\r\n\r\npublic record Book(int id, string title, string author, int publishedYear);<\/code><\/pre>\nJsonContent.Create<\/code> overloads accepting JsonTypeInfo<\/code><\/h3>\nJsonContent<\/code> instances using trim safe\/source generated contracts:<\/p>\nvar book = new Book(id: 42, \"Title\", \"Author\", publishedYear: 2023);\r\nHttpContent content = JsonContent.Create(book, MyContext.Default.Book);\r\n\r\npublic record Book(int id, string title, string author, int publishedYear);\r\n\r\n[JsonSerializable(typeof(Book))]\r\npublic partial class MyContext : JsonSerializerContext \r\n{ }<\/code><\/pre>\nJsonNode.ParseAsync<\/code> APIs<\/h3>\nJsonNode<\/code> instances from streams:<\/p>\nusing var stream = File.OpenRead(\"myFile.json\");\r\nJsonNode node = await JsonNode.ParseAsync(stream);<\/code><\/pre>\nJsonSerializerOptions.MakeReadOnly(bool populateMissingResolver)<\/code><\/h3>\nJsonSerializerOptions.MakeReadOnly()<\/code> method was designed to be trim-safe and will therefore throw an exception in cases where the options instance hasn’t been configured with a resolver.<\/p>\noptions.MakeReadOnly(populateMissingResolver: true);<\/code><\/pre>\nJsonSerializer<\/code> methods that accept JsonSerializerOptions<\/code>. A side-effect of that behavior is that the new overload is marked RequiresUnreferenceCode<\/code>\/RequiresDynamicCode<\/code> and is therefore unsuitable for Native AOT applications.<\/p>\nAndroidStripILAfterAOT<\/code> mode on Android<\/h2>\nRelease<\/code> mode. AOT compilation results in faster startup time and runtime performance improvements at the expense of a larger app size. Profiled AOT, only AOT compiles a portion of your application’s startup path — improving startup time, with a minimal increase to application size. The new AndroidStripILAfterAOT<\/code> setting removes unused IL that was AOT-compiled, reducing the apk size by at least 0 – 3.5% for a dotnet template application.<\/p>\nWhen to consider using
AndroidStripILAfterAOT<\/code>:<\/h3>\n$(AndroidStripILAfterAOT)<\/code> goes a step further to remove the unused IL, making the app size increase from AOT-compilation more reasonable. The removed IL will also no longer be present, making it more difficult (but not impossible) to reverse engineer your application’s .NET code.<\/p>\nHow to use
AndroidStripILAfterAOT<\/code>:<\/h3>\n<PropertyGroup Condition=\" '$(Configuration)' == 'Release' \">\r\n <AndroidStripILAfterAOT>true<\/AndroidStripILAfterAOT>\r\n<\/PropertyGroup><\/code><\/pre>\nAndroidStripILAfterAOT<\/code> to true will override<\/em> the default AndroidEnableProfiledAot<\/code> setting, allowing all trimmable AOT’d methods to be removed. Profiled AOT and IL stripping can be used together by explicitly setting both:<\/p>\n<PropertyGroup Condition=\" '$(Configuration)' == 'Release' \">\r\n <AndroidStripILAfterAOT>true<\/AndroidStripILAfterAOT>\r\n <AndroidEnableProfiledAot>true<\/AndroidEnableProfiledAot>\r\n<\/PropertyGroup><\/code><\/pre>\n.apk<\/code> size results for a dotnet new android<\/code> app:<\/p>\n
![](\"https:\/\/devblogs.microsoft.com\/dotnet\/wp-content\/uploads\/sites\/10\/2023\/09\/community-spotlight.png\")
<\/p>\n