.NET 11 Preview 3 updates archive validation and text handling

Microsoft released .NET 11 Preview 3 on April 14 with changes across the runtime, libraries, and SDK. For application maintainers, the announcement highlights two useful compatibility surfaces: reading compressed archives and recognizing newline sequences.

Input handling deserves representative fixtures

The preview adds CRC32 validation to ZIP reads, moves Zstandard into System.IO.Compression, and expands regular-expression recognition of Unicode newline sequences. SDK updates include command-line editing of solution filters and splitting file-based applications across files.

A focused evaluation should begin with the data the application actually accepts. For an archive importer, include truncated and damaged fixtures as well as successful files. The meaningful observation is how the application reports failure and whether partially processed content is handled consistently. A stricter library check is useful only when its result reaches the caller in an understandable form.

Keep text semantics visible

For text-processing code, compare line-oriented behavior across the character sequences present in customer inputs. A parser, validator, and display layer may each have a different idea of where a line ends. Pinning those expectations in a small fixture set makes an interpreter or library upgrade easier to assess.

The SDK changes also invite a cleanup of small utilities, but that work need not accompany the compatibility experiment. First establish that the same application behavior holds under the preview; then consider whether its project layout becomes easier to maintain.

Because this is a preview release, record the exact SDK used in any issue report. A concise example containing the input and observed output is more useful feedback than a broad report that an entire import pipeline behaves differently.