RepoJournal
.NET

@dotnet

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

Pick a date

  1. Wed 20 may
  2. Thu 21 may
  3. Sat 23 may
  4. Sun 24 may
  5. Mon 25 may
  6. Tue 26 may
  7. Wed 27 may
  8. Thu 28 may
  9. Fri 29 may
  10. Sat 30 may
  11. Sun 31 may
  12. Mon 1 jun
  13. Mon 8 jun
  14. Tue 9 jun
  15. Wed 10 jun
  16. Thu 11 jun
  17. Fri 12 jun
  18. Sat 13 jun
  19. Sun 14 jun
  20. Mon 15 jun
  21. Tue 16 jun
  22. Wed 17 jun
  23. Thu 18 jun
  24. Sat 27 jun
  25. Sun 28 jun
  26. Mon 29 jun
  27. Tue 30 jun
  28. Wed 1 jul
  29. Thu 2 jul
  30. Today 3 jul

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].

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

FAQ

What changed 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.
What should .NET teams do about it?
If shipping Android NativeAOT apps, verify crypto JNI exports are retained in final APK after patching • Monitor wasm/CoreCLR outerloop results for slow test suite regressions in your dependencies • Update WinForms if ToolStripScrollDownButton exceptions appear in dropdown menus
Which .NET repositories shipped on July 1, 2026?
dotnet/runtime, dotnet/winforms, dotnet/dotnet

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.