SevenZipSharp

SevenZipSharp copied to clipboard

Currently all versions contain the 1.0.0.0 version. Any reason why it's not being updated? `1.0.0.0 1.0.0.0 1.0.0.0`

MarcWeintraub

I started by asking why archives should be marked as Solid by default #161 Then I wondered by 7Zip wouldn't know how to extract a file from a Solid archive...

doug24

Is there a method to check whether an archive stream/file is encrypted?

1

I tried to found in SevenZipExtractor but couldn't found one?

hiwhitesu

I'm hoping someone has some insight to the 'Solid' property setting in archives. Are there really archive formats that are Solid archives but not marked with the Solid property =...

doug24

ExtractArchive decided wrong format

5

Hi, I am using sevenzipsharp and I have a lot of archives that are msi, rar, iso and more formats that ExtractArchive decided it is TAR and because of that...

roee01

I have an exception in SevenZipExtractor.BeginExtractArchive(string directory) when unpacking a stream

7

``` var zipStream = new FileStream("c:\\backup\\file.zip", FileMode.Open); SevenZip.SevenZipBase.SetLibraryPath("x86\\7z.dll"); var z = new SevenZip.SevenZipExtractor(zipStream, "pass"); z.BeginExtractArchive("c:\\tmp\\test_ext"); ``` .net 4.5.2 **The specified stream can not seek or read. Имя параметра: stream** Server...

altbodhi

Listing all files from SevenZipExtractor's ArchiveFileData collection gives every detail about any file entry. However it just reports the unpacked size of a file and not its packed size. Will...

zipgenius

Like This  Process will throw this exception near the end. (.NET 6, 7z.dll is 19.00) 

HarrisWilde

I am getting following exception while trying to append a new file to an existing password protected 7z archive.  Exception occurs while invoking CompressFilesEncrypted method in append mode, as...

amarendrabiorad

NuGet package Squid-Box.SevenZipSharp 1.5.0.366 includes DLLs with version 1.0.0.0

1

I'm using the NuGet package Squid-Box.SevenZipSharp in a .NET 4.8 application that is deployed via MSI. After updating from NuGet package version 1.3.283 to 1.5.0.366 I noticed a strange behaviour...

Toqe