Libraries and runtime updates in .NET 9 Preview 7

[richlander]

Lots new this release to try out.

📚Libraries

• Removal of BinaryFormatter is complete
• Enumerate over ReadOnlySpan<char>.Split() segments
• Debug.Assert now reports assert condition, by default.
• Compression APIs now use zlib-ng
• Guid.CreateVersion7 enables creating GUIDs with a natural sort order
• Interlocked.CompareExchange for more types
• AES-GCM and ChaChaPoly1305 algorithms enabled for iOS/tvOS/MacCatalyst
• Changes to X.509 Certificate Loading
• Support for XPS documents from XPS virtual printer
• Marking Tensor<T> as Experimental
• Full release notes

⏱️Runtime

• ARM64 SVE Support
• Post-Indexed Addressing on ARM64
• Strength Reduction in Loops
• Object Stack Allocation for Boxes
• GC Dynamic Adaptation To Application Sizes
• Full release notes

Release notes:

• Libraries release notes
• Runtime release notes

.NET 9 Preview 7:

• Discussion
• Release notes
• What's new in .NET 9

[ReneeGA2020]

wasm import export sample seems to be broken in this preview:
https://github.com/dotnet/runtime/tree/main/src/mono/sample/wasi/native

I got this error when try to ran the sample.

Error: cannot execute a component without --wasm component-model

Seems like the wasmtime recognize the output wasm file to be a component instead of executable wasm file.

[richlander]

@lewing

[pavelsavara]

@ReneeGA2020 note that WASI target is quite immature experiment, not a supported target. It's not part of the Net9 release and not really part of the Net9 previews.

We are making some more progress on main branch of the repository and we don't plan to backport fixes to Net9. If you don't want to build your own runtime from sources, you are probably better off by downloading one of the nightly builds

Regarding this particular issue is probably caused by old version of wasmtime installed on your machine, but I'm not sure. We switched to producing WASI preview2, component model binaries some time ago.

Anyway, this preview7 announcement is not right place to troubleshoot it.
Please feel free to open separate issue and ping me on it, thank you.

[ReneeGA2020]

Oh, thank you, this issue was actually addressed in another tick 2 weeks ago. I forgot to update here.
#106523

Thank for the .net team's work.