Since this repo seems to be died, I ceated a fork:
https://github.com/zgabi/ManagedXZ

And a new nuget package:
https://www.nuget.org/packages/zgabi.ManagedXZ/

It contains the fixes for #8 & #9 and also implmented the request #10 (added .NET 6 target, since netstandard is made deprecated meanwhile)

All PRs welcome.

currently I use the default preset 6
should allow users to choose preset

In netstandard 2.1 it is possible to directly read/write from/to .net Steams using Span
For example:
var bytesRead = _stream.Read(new Span<byte>((byte*)_inbuf, BUFSIZE));

This needs the AllowUnsafeBlocks in the project file, but will be as safe as the current Marshal.Copy.

So the package could target both netstandard2.0 and netstandard2.1, and in the netstandard 2.1 version in could use Spans.

compare the performance of the wrapper and native xz.exe
the wrapper made several memory copies during encode and decode, may hurt the performance

Hi,

It's not a PR because I understand you won't merge this, but take a look at my fork. The difference I made is that the dll's are retrieved from the /bin folder. Your version looked in a temporary folder (where ManagedXZ.dll was stored, but lzma files weren't.)

Thanks for all your effort!

Hello, so I'm trying to create an compression program that uses XZ format. The other ones I saw used LZMA, which doesn't support multithreading. However, I'm not sure how to make use of this for directories, I only know how to use this for files.
Any help would be appreciated, thanks.

to detect possible memory leaks

Hi,

Please use System.Buffers.ArrayPool to get a new buffer in the following lines:

And maybe in the XZUtils.

They are just temporary buffers, and can be returned in the end of the code block with: ArrayPool<byte>.Shared.Return(data);

Thank you.

0 byte files, 1 byte files, etc.

Reading through the source, I noticed the following:
https://github.com/goldenbull/ManagedXZ/blob/master/src/ManagedXZ/XZDecompressStream.cs#L82

Stream.Read may return less than the requested bytes for any number of reasons, not only when it has reached the end of a Stream.

For instance, NetworkStream will return the number of bytes currently available, even if that's less than the number requested. Zero bytes is the only special case, which indicates EndOfStream.

I think you should just check for zero here and send LZMA_FINISH in that case. Otherwise just push through whatever data you got from the Read.

Unhandled exception. System.TypeInitializationException: The type initializer for 'ManagedXZ.Native' threw an exception.
---> System.ArgumentNullException: Value cannot be null. (Parameter 'path1')
at System.IO.Path.Combine(String path1, String path2)
at ManagedXZ.Native..cctor()
--- End of inner exception stack trace ---
at ManagedXZ.XZDecompressStream.Init()
at ManagedXZ.XZDecompressStream..ctor(Stream stream)
at AisStreamer.Program.Main(String[] args)

Problem occurs when PublishSingleFile is true (.net core 3+). In this case the executing assembly's location is empty.

Would you accept a PR for fixing this and also fixing my other issue (#8)?