Skip to content

Behavior change regarding seekability of streams returned for ZipArchive #585

Closed
@ojhad

Description

@ojhad
  • .NET Core Version: 3.0.100-preview4

Problem description:

There is a behavior change regarding the seekability of returned ZipArchiveEntry streams.

.NET Framework behavior:

The WindowsBase implementation of Zip had the necessary functionality that operated on the returned deflate streams which provided support for seeking (However, in doing so, it incurred a lot of extra CPU and file system usage)

.NET Core behavior:
The current implementation in CoreFX (System.IO.Packaging) no longer provides this functionality, resulting in streams that are being returned to be non-seekable.

Related Issue:
https://github.com/dotnet/corefx/issues/34219

Metadata

Metadata

Assignees

Labels

BugProduct bug (most likely)rank20Rank: Priority/rank on a scale of (1..100)regressionstatus: This issue is a regression from a previous build or release

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions