Compiler error when importing via UPM about zstring HOT 9 CLOSED

upm package does not include managed dlls.
https://github.com/Cysharp/ZString/tree/master/src/ZString.Unity/Assets/Plugins
require to add manually(outside of package).

from zstring.

There are UPM packages that provide DLLS, though. Is there any reason those DLLs can't be split off into separate packages that ZString uses as a dependency?

from zstring.

Other packages that using System.Memory etc(ZLogger, MessagePack-CSharp, etc) are exists.
If you include System.Memory, etc., the possibility of conflicts occurs.

from zstring.

Those are all your packages, right? So can't you make all of them depend on these DLLs (or just the ones that they need at least)? Given how popular your packages are, I bet if you wrapped System.Memory and the like in UPM packages everyone would coalesce around them quickly.

from zstring.

These packages are certainly under my control, but System.* itself is used by others, so there is always the possibility of conflicts.
Unity does not have a binding redirection mechanism, so if the dll versions are different, it will not work properly.
Unless the UPM mechanism itself changes (or unless System.Memory is included in the standard libs to support netstandard2.1/net5), there is no good solution.

from zstring.

Dang. Is there any reason you couldn't prepare a package containing a version of these libraries that's known to work with your packages but is technically an optional dependency? Right now ZString and ZLogger are the only libraries I use that require System.Memory and company (and if that changes I'll worry about it then).

from zstring.

i recommend using the samples of the package just to import the dlls

from zstring.

Yeah that's what I do now, but I'd rather keep dependencies out of my git repo where possible.

from zstring.

merged, thanks all.

from zstring.