Quantcast
Channel: Questions in topic: "dll"
Viewing all articles
Browse latest Browse all 706

Two libraries with the same libraries but different version of it

$
0
0

Hi,

I've been banging my head on my desk for 3 days straight trying to make this work but I have to submit and ask for help at this point as I have no more ideas.

Here's the situtation.

I'm trying to use "ImageSharp" to draw and create images and produce a png that's going to be mainly for debugging purpose for now. (Basically just drawing the debug version of a procedurally generated map) ImageSharp has 3 libraries I need. It was working just fine in my side project to code the generator in vscode (outside of unity) but once I integrated evreything in unity, ImageSharp return an error saying "System.Runtime.CompilerServices.Unsafe" reference is the wrong version. Problem is that 2 of the libraries use a version of unsafe that is different from the third. It was managed in vscode automatically and worked just fine but unity doesn't like it and it seems to conflict with some unity librairies. (I'm not too sure if it's still relevant but I've seen post on the forum about this) So I have tried a lot of stuff over the last few days but here's the gist of what I've tried: - Installing ImageSharp through NugetForUnity but I basically got the same thing. - Another nuget manager from someone internal at unity but only a few packages were available (Including unsafe and imagesharp) but only the main imageSharp was there since the other two are preview packages - Compile every .dll, including both imageSharp(s) and unsafe both version. Create two folder in plugin with their respective dll - Tried to create an assembly reference for those imageSharp dll so they could point to their respective dll - Re-organize my whole project in sub-section with assembly, so the assembly that needs imageSharp could reference it. However, it was requiring that I override the reference, which seems to make it worse. They all failed and I'm not sure if I was close to the solution at some point or not. I have this right now: - ImageSharp.dll - ImageSharp.Font.dll - ImageSharp.Drawing.dll - System.Runtime.CompilerServices.Unsafe_4.0.6.0.dll (font) - System.Runtime.CompilerServices.Unsafe_5.0.0.0.dll (base + drawing) How do I organise this so they can both use they're own dll? One thing I want to make clear. If I delete one of the dll, the errors for the other dll go away as they now have the right one, but other is missing it's dll and vice-versa. So I know they'll work If I just manage to force them to use the right one. Thanks for anyone who can help clean this up for me.

Viewing all articles
Browse latest Browse all 706

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>