SharpCompress -Update from 0.445 to 0.46.3 produces error

Question

SharpCompress -Update from 0.445 to 0.46.3 produces error

Pip 265

Hi,

I'm using class library of .NET 10.

<TargetFrameworks>net10.0</TargetFrameworks>

I update from 0.445 to 0.46.3 produces errors User's image

 using (var archive = ArchiveFactory.Open(archivePath))
 {
     var list = new List<string>();
     foreach (var entry in archive.Entries)

Error:

'ArchiveFactory' does not contain a definition for 'Open'

What to do?

Thanks in advance,

Answer accepted by question author

1 additional answer

Your answer

Answer 1

Jack Dang (WICLOUD CORPORATION) 14,955 Microsoft External Staff Moderator

Hi @Pip ,

Thanks for reaching out.

In SharpCompress version 0.46.x, the Open() method was removed and replaced with OpenArchive() for synchronous usage and OpenAsyncArchive() for asynchronous usage. So that’s why your old code is now showing:

'ArchiveFactory' does not contain a definition for 'Open'

Here’s some guidance on choosing between them:

Small archive files or simple scenarios: use OpenArchive(). It behaves just like your old Open() method, everything happens step by step.
Large archive files or when you don’t want your app to freeze while loading: use OpenAsyncArchive() inside an async method with await. This lets your program do other things while the archive is being read.

Example using synchronous OpenArchive():

using var archive = ArchiveFactory.OpenArchive(archivePath);
foreach (var entry in archive.Entries)
{
    // process entries here
}

Example using asynchronous OpenAsyncArchive():

public async Task ProcessArchiveAsync(string archivePath)
{
    using var archive = await ArchiveFactory.OpenAsyncArchive(archivePath);
    foreach (var entry in archive.Entries)
    {
        // process entries here
    }
}

Note: Please use these code snippets as reference only, adjust them to fit your project’s structure, async/sync needs, and error handling.

Hope this helps! If my answer was helpful - kindly follow the instructions here so others with the same problem can benefit as well.

Pip 265 Reputation points

2026-03-02T08:29:01.49+00:00

Hi @Jack Dang (WICLOUD CORPORATION)

What consider small files and what consider large files?

It possible to handle both cases ?

Thanks,
Jack Dang (WICLOUD CORPORATION) 14,955 Reputation points Microsoft External Staff Moderator

2026-03-02T08:39:20.89+00:00
Hi @Pip ,

There isn’t a strict rule for what counts as “small” or “large.” It really depends on how long the file takes to open and whether blocking the thread is a problem in your app.

As a rough idea:

Small = a few MBs up to maybe 50–100 MB (opens quickly, no noticeable delay)

Large = hundreds of MBs or more (can take time and block the thread)

The more important factor isn’t the exact size, it’s your app type. If this is a web app or UI app, it’s better to use OpenAsyncArchive() so you don’t block the thread. If it’s a simple console or background tool, OpenArchive() is totally fine.

And yes, you can handle both cases. In fact, the simplest and cleanest approach is to just use the async version everywhere (if your project supports async). It works for both small and large files, and you don’t need special size checks.
Pip 265 Reputation points

2026-03-02T08:49:25.63+00:00

I used this function in my Lib internally.

The console app (CLI App) consumes it, so is it fine to use OpenArchive ?

It will handle also large files (in blocking manner)?
Jack Dang (WICLOUD CORPORATION) 14,955 Reputation points Microsoft External Staff Moderator

2026-03-02T08:56:08.87+00:00

Hi @Pip ,

In your case, it’s fine to use OpenArchive().

Since your library is used by a console (CLI) app, blocking is not really an issue. Console apps naturally wait for operations to finish anyway.

And yes, it will handle large files too - it will just process them in a blocking way, meaning the app waits until it’s done. That’s normal for a CLI tool.

Answer 2

Giovanni Savoretti 0

Hi Pip,

The Open() function has been replaced with two other functions: OpenArchive() and OpenAsyncArchive().

Prefer OpenAsyncArchive() if you are working with an asynchronous method.

Pip 265 Reputation points

2026-03-01T20:12:52.7533333+00:00

Till now I used Open() function, I think it was synchronous? is it?

Which one to use ? OpenArchive() or OpenAsyncArchive() ?

The input file can be big or small archive files ? so which one to use ? what is the best practice ?

If it async function to use it in that way:

using (var archive = await ArchiveFactory.OpenAsyncArchive(archivePath))

Share via

SharpCompress -Update from 0.445 to 0.46.3 produces error

1 additional answer

Your answer