Repository navigation
Releases
NetWasm.Libraries 0.15.0
This release builds the libraries for net10.0-netwasm, NetWasm 0.15's .NET platform target framework, against NetWasm 0.15.0 and TUnit-NetWasm 0.15.0.
- Microsoft's own
Microsoft.Extensions.Primitives,Microsoft.Extensions.Configuration(with its abstractions and the environment-variable, command-line and JSON providers),Microsoft.Extensions.Caching.Abstractions,System.IO.HashingandSystem.Formats.Cborpackages run onnet10.0-netwasmunchanged. Their ports are retired, and the remaining libraries depend on Microsoft's packages. - Configuration binding converts values as upstream's
TypeConverters do. - A project that still targets the deprecated
netwasm0.1keeps using the 0.14 packages.
The repository builds 9 packages. CI runs every package's tests on net10.0-netwasm.
See the release changes in #32.
NetWasm.Libraries 0.15.0 Preview 1
This release builds the libraries for net10.0-netwasm, NetWasm 0.15's .NET platform target framework, against NetWasm 0.15.0 and TUnit-NetWasm 0.15.0.
- Microsoft's own
Microsoft.Extensions.Primitives,Microsoft.Extensions.Configuration(with its abstractions and the environment-variable, command-line and JSON providers),Microsoft.Extensions.Caching.Abstractions,System.IO.HashingandSystem.Formats.Cborpackages run onnet10.0-netwasmunchanged. Their ports are retired, and the remaining libraries depend on Microsoft's packages. - Configuration binding converts values as upstream's
TypeConverters do. - A project that still targets the deprecated
netwasm0.1keeps using the 0.14 packages.
The repository builds 9 packages. CI runs every package's tests on net10.0-netwasm.
See the release changes in #32.
NetWasm.Libraries 0.14.3
This release gives the ported libraries the identity of the assemblies they port, so NuGet packages compiled against Microsoft's Microsoft.Extensions.*, System.Formats.Cbor and System.IO.Hashing assemblies use NetWasm's ports. It builds against NetWasm 0.14.2 and TUnit-NetWasm 0.14.2, like 0.14.2.
- Each assembly carries upstream's public key and assembly version 11.0.1.0. Microsoft keeps 11.0.0.0 for every 11.x release, so the port also wins when an application restores Microsoft's package beside it.
- Until now the assemblies were version 0.0.0.0. A package compiled against Microsoft's
Microsoft.Extensions.DependencyInjection.Abstractions, such as a container extension, failed to compile (CS0012). Or, through its dependency on Microsoft's package, it replaced the port, so the application ran Microsoft's container contracts instead of NetWasm's. - The file and informational versions carry the release version, and the source generators carry it as their assembly version.
The repository builds 18 packages. CI runs the library suites twice, unoptimized and at O3 with NetWasmGC.
See the release changes in #31.
NetWasm.Libraries 0.14.3 Preview 1
This release gives the ported libraries the identity of the assemblies they port, so NuGet packages compiled against Microsoft's Microsoft.Extensions.*, System.Formats.Cbor and System.IO.Hashing assemblies use NetWasm's ports. It builds against NetWasm 0.14.2 and TUnit-NetWasm 0.14.2, like 0.14.2.
- Each assembly carries upstream's public key and assembly version 11.0.1.0. Microsoft keeps 11.0.0.0 for every 11.x release, so the port also wins when an application restores Microsoft's package beside it.
- Until now the assemblies were version 0.0.0.0. A package compiled against Microsoft's
Microsoft.Extensions.DependencyInjection.Abstractions, such as a container extension, failed to compile (CS0012). Or, through its dependency on Microsoft's package, it replaced the port, so the application ran Microsoft's container contracts instead of NetWasm's. - The file and informational versions carry the release version, and the source generators carry it as their assembly version.
The repository builds 18 packages. CI runs the library suites twice, unoptimized and at O3 with NetWasmGC.
See the release changes in #31.
NetWasm.Libraries 0.14.2
This release builds the libraries against NetWasm 0.14.2 and TUnit-NetWasm 0.14.2. It is the first Libraries release for NetWasm 0.14.
- The libraries that ship with .NET itself now come with
NetWasm.Sdkas part ofNetWasm.App: LINQ, Async LINQ, Memory, Pipelines, Encodings.Web, HTTP and HTTP JSON, regular expressions, JSON, XML, Data.Common, DataContract serialization and Net.Requests. TheirNetWasm.System.*packages are not released again, and the out-of-band packages (Configuration.Json, Http, CBOR and hashing among them) no longer depend on them. The 0.13.0 packages stay on NuGet.org for applications on NetWasm 0.13 and earlier. See the NetWasm 0.14.0 release, including its upgrading notes. IOptions<T>resolves to upstream's internalUnnamedOptionsManager<T>, as on .NET, in place of the publicOptionsManager<T>. The Options library's own generated factory activates it, so applications never name the internal type.- NetWasm's own sources (the generators and tools, the generated-activation runtime and the tests) start with a notice naming NetWasm and their license; files ported from upstream keep upstream's notice.
LICENSES/MIT.txtnames its copyright holder.
The repository builds 18 packages. CI runs the library suites twice, unoptimized and at O3 with NetWasmGC, so every optimization meets the libraries' code. The NetWasm compiler and test runner are qualified on every supported host by NetWasm and TUnit-NetWasm.
See the release changes in #29.
NetWasm.Libraries 0.14.2 Preview 1
This release builds the libraries against NetWasm 0.14.2 and TUnit-NetWasm 0.14.2. It is the first Libraries release for NetWasm 0.14.
- The libraries that ship with .NET itself now come with
NetWasm.Sdkas part ofNetWasm.App: LINQ, Async LINQ, Memory, Pipelines, Encodings.Web, HTTP and HTTP JSON, regular expressions, JSON, XML, Data.Common, DataContract serialization and Net.Requests. TheirNetWasm.System.*packages are not released again, and the out-of-band packages (Configuration.Json, Http, CBOR and hashing among them) no longer depend on them. The 0.13.0 packages stay on NuGet.org for applications on NetWasm 0.13 and earlier. See the NetWasm 0.14.0 release, including its upgrading notes. IOptions<T>resolves to upstream's internalUnnamedOptionsManager<T>, as on .NET, in place of the publicOptionsManager<T>. The Options library's own generated factory activates it, so applications never name the internal type.- NetWasm's own sources (the generators and tools, the generated-activation runtime and the tests) start with a notice naming NetWasm and their license; files ported from upstream keep upstream's notice.
LICENSES/MIT.txtnames its copyright holder.
The repository builds 18 packages. CI runs the library suites twice, unoptimized and at O3 with NetWasmGC, so every optimization meets the libraries' code. The NetWasm compiler and test runner are qualified on every supported host by NetWasm and TUnit-NetWasm.
See the release changes in #29.
NetWasm.Libraries 0.13.0
This release builds the libraries against NetWasm 0.13.0 and TUnit-NetWasm 0.13.0. The library code is unchanged.
- NetWasm 0.13.0 programs carry no type names: a type's name reads
type#<id>unless the build writes the program's names beside it. The libraries' only type-name checks, in System.Text.Json, are already left out of NetWasm builds, so the libraries behave as before. See the NetWasm 0.13.0 release.
CI runs the library suites twice, unoptimized and at O3 with NetWasmGC, so every optimization meets the libraries' code. The NetWasm compiler and test runner are qualified on every supported host by NetWasm and TUnit-NetWasm.
See the release changes in #28.
NetWasm.Libraries 0.13.0 Preview 1
This release builds the libraries against NetWasm 0.13.0 and TUnit-NetWasm 0.13.0. The library code is unchanged.
- NetWasm 0.13.0 programs carry no type names: a type's name reads
type#<id>unless the build writes the program's names beside it. The libraries' only type-name checks, in System.Text.Json, are already left out of NetWasm builds, so the libraries behave as before. See the NetWasm 0.13.0 release.
CI runs the library suites twice, unoptimized and at O3 with NetWasmGC, so every optimization meets the libraries' code. The NetWasm compiler and test runner are qualified on every supported host by NetWasm and TUnit-NetWasm.
See the release changes in #28.
NetWasm.Libraries 0.12.1
This release fixes HttpClient for responses whose headers .NET's header parser would reject.
NetWasm.System.Net.Httptakes a received header as .NET's handlers do: as sent, without validating its value. A response that carries, for example, an unquotedETag, as Azure storage and CDNs send, no longer fails with aFormatException(#215).
CI runs the library suites twice, unoptimized and at O3 with NetWasmGC, so every optimization meets the libraries' code. The NetWasm compiler and test runner are qualified on every supported host by NetWasm and TUnit-NetWasm.
See the release changes in #27.
NetWasm.Libraries 0.12.1 Preview 1
This release fixes HttpClient for responses whose headers .NET's header parser would reject.
NetWasm.System.Net.Httptakes a received header as .NET's handlers do: as sent, without validating its value. A response that carries, for example, an unquotedETag, as Azure storage and CDNs send, no longer fails with aFormatException(#215).
CI runs the library suites twice, unoptimized and at O3 with NetWasmGC, so every optimization meets the libraries' code. The NetWasm compiler and test runner are qualified on every supported host by NetWasm and TUnit-NetWasm.
See the release changes in #27.