RepoJournal
.NET

@dotnet

The .NET runtime, ASP.NET, and the C# tooling

Keep up with .NET in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: .NET Full archive →

The Wire · Showcase

RUNTIME LANDS ANDROID NATIVEAOT FIX, WASM CORECLR TESTING EXPANDS

By RepoJournal · Filed · About .NET

Android NativeAOT apps can now properly export crypto JNI callbacks, while the runtime team shipped outerloop CI coverage for wasm/CoreCLR to finally catch slow suite regressions.

The Android fix [1] resolves a critical packaging gap where the crypto trust-manager JNI callback wasn't being retained in final APK binaries, unblocking customer NativeAOT deployments on mobile. That same team simultaneously shipped wasm/CoreCLR outerloop CI [2], which runs the full slow test suites on single-threaded wasm for the first time, catching regressions that desktop and Mono browser builds miss. On the API front, Process.Start gained platform-specific callback overloads [3] letting callers inject custom Windows and Unix process creation logic while staying within Process infrastructure for stream handling and lifecycle management. The reflection-based XmlSerializer now handles XmlSchemaObject-derived types correctly [4] by matching IL-reader behavior on schema name encoding. WinForms shipped a ToolStripScrollDownButton fix [5] that prevents exceptions when the last item is visible, and fixed NumericUpDown button rendering [6] when visual styles are disabled. The monorepo continues ingesting from runtime, efcore, SDK, and F# [7] [8] [9] [10].

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] Fix Android NativeAOT test crypto JNI export (#129872) dotnet/runtime
  2. [2] [browser][coreclr] Add wasm/CoreCLR libraries tests to outerloop CI (#129436) dotnet/runtime
  3. [3] Add Process.Start callback overload with WindowsProcessStartArguments and UnixProcessStartArguments ↗ dotnet/runtime
  4. [4] Fix reflection-based XmlSerializer to support XmlSchemaObject-derived types ↗ dotnet/runtime
  5. [5] Issue 6650 fix strip scroll down button scroll exception (#14537) dotnet/winforms
  6. [6] Fix NumericUpDown button rendering regression when visual styles are disabled (#14643) dotnet/winforms
  7. [7] [main] Source code updates from dotnet/runtime ↗ dotnet/dotnet
  8. [8] [main] Source code updates from dotnet/efcore ↗ dotnet/dotnet
  9. [9] [main] Source code updates from dotnet/sdk ↗ dotnet/dotnet
  10. [10] [main] Source code updates from dotnet/fsharp ↗ dotnet/dotnet

Quick answers

What shipped in .NET on July 1, 2026?
Android NativeAOT apps can now properly export crypto JNI callbacks, while the runtime team shipped outerloop CI coverage for wasm/CoreCLR to finally catch slow suite regressions. In total, 52 commits, 52 pull requests, and 1 releases landed.
Who contributed to .NET on July 1, 2026?
3 developers shipped this update, including Copilot, StephenMolloy, and dotnet-maestro[bot].
What were the notable .NET updates?
Fix Android NativeAOT test crypto JNI export (#129872), [browser][coreclr] Add wasm/CoreCLR libraries tests to outerloop CI (#129436), and Add Process.Start callback overload with WindowsProcessStartArguments and UnixProcessStartArguments.

More from @dotnet

Daily updates, in your inbox

Follow .NET

Keep up with .NET in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.