You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The .zip file was created on Windows. I'm not sure if that matters or not.
In ExtractionMethods.WriteEntryToDirectory the second line makes a call to Path.GetFileName(entry.Key). The key looks like "a\\b.txt". Since this is running on Linux the file name I get back is "a\\b.txt" instead of "b.txt". This is causing all the files to have names like a\b.txt instead of creating the folder structure and putting the file in it.
The text was updated successfully, but these errors were encountered:
Looks like zips created with 7zip and with Windows Send to Compressed (zipped) folder both create entries with keys using / and not \. I'll figure out how this file was created.
I don't believe it is. Slashes mean directories in zip keys. If there's an extra one, that's not the fault of the decoder. The encoder shouldn't have it.
The .zip file was created on Windows. I'm not sure if that matters or not.
In
ExtractionMethods.WriteEntryToDirectory
the second line makes a call toPath.GetFileName(entry.Key)
. The key looks like"a\\b.txt"
. Since this is running on Linux the file name I get back is"a\\b.txt"
instead of"b.txt"
. This is causing all the files to have names likea\b.txt
instead of creating the folder structure and putting the file in it.The text was updated successfully, but these errors were encountered: