$ the-wire · showcase
Vector literals stop breaking under comma-decimal cultures, AIDL one-way proxies generate correctly
By RepoJournal · Filed · About .NET · Composed from the cited sources · methodology
15 people shipped this
AbhitejJohn
@AbhitejJohn
2 cited
albyrock87
@albyrock87
1 cited
jasonmalinowski
@jasonmalinowski
1 cited
jonathanpeppers
@jonathanpeppers
1 cited
simonrozsival
@simonrozsival
1 cited
ilkertskn
@ilkertskn
1 cited
PureWeen
@PureWeen
praveenkumarkarunanithi
@praveenkumarkarunanithi
dependabot
@dependabot
kotlarmilos
@kotlarmilos
Amaury Levé
@Evangelink
AlekseyTs
@AlekseyTs
JoeRobich
@JoeRobich
RikkiGibson
@RikkiGibson
RoderickIveans
@RoderickIveans
Two correctness fixes land in places that fail quietly: EF Core's SQL literal formatting under non-invariant cultures, and the Android AIDL generator's handling of method-level oneway semantics.
Format vector floats with the invariant culture dotnet/efcore
GenerateNonNullSqlLiteral was appending each float through StringBuilder.Append(float), which formats with the current culture, so a vector literal like CAST('[1.5,2.5]' AS VECTOR(2)) came out as CAST('[1,5,2,5]' AS VECTOR(2)) on de-DE and any other comma-decimal locale. Floats now format with the "R" specifier and CultureInfo.InvariantCulture, matching FloatTypeMapping, with a regression test ...
Fix AIDL one-way proxy generation dotnet/android
Generated AIDL proxy methods now honor method-level oneway semantics: the reply Parcel is omitted, null is passed, TransactionFlags.Oneway is used, and ReadException() is skipped. Reply Parcels for synchronous void proxy methods are also recycled on both success and exception paths, and the generator's golden outputs were updated.
Remove build-time Java resources from APKs dotnet/android
Nested JARs, Kotlin Multiplatform metadata, R.txt, ProGuard/R8 rules, and AAR metadata no longer ship inside APKs and AABs; anchored defaults were added to AndroidPackagingOptionsExclude in AutoImport.in.props. Runtime resources such as META-INF/services and Kotlin builtins are preserved. Expect smaller outputs, and check any build step that read those files out of the archive.
Revert Vally CLI 0.16 upgrade dotnet/skills
@microsoft/vally-cli goes back from 0.16.0 to 0.14.0 along with the prior lockfile graph. Vally 0.16.0 rejects eval syntax that 0.14.0 accepts, and on main 90 of 101 eval specs use at least one incompatible construct (legacy top-level config, repository executionShard metadata, or the removed expect_tools and reject_tools constraints), failing while loading rather than during model execution.
[iOS] ScrollView: Keep the content offset when the scroll view is resized by its parent layout dotnet/maui
On iOS, a ScrollView resized by its parent in the same pass that its content outgrows the viewport ended up scrolled by half the resize delta, leaving the first item partly hidden; the fix retains the content offset. The trigger is the common bound-page shape: a Grid with Auto,*,Auto rows, the ScrollView in the star row, and content plus an Auto-row footer arriving from the ViewModel after the ...
Restore the built-in VS SDK .pkgdef generation and migrate to it dotnet/roslyn
Roslyn restores the built-in VS SDK GeneratePkgDef target after having replaced it with a custom MSBuild target that disabled the standard RegistrationAttribute-based system, and migrates to the attributes it can. The custom pieces worth keeping stay in place.
Harden DevOps health investigation and reporting dotnet/skills
The long tail: DevOps health investigation was hardened so an absent optional known-noise cache value is treated as an empty list, noop is no longer emitted after another successful output, the documented two-worker investigation limit is enforced in both source and compiled workflow, and every health-check, groomer, and investigator issue mutation binds to the canonical dashboard.
Action items
