DLL conflicts with Cysharp packages about classtypereference-for-unity HOT 2 CLOSED

On Tue, Feb 16, 2021 at 7:12 PM Artem ***@***.***> wrote: I see Cysharp closed the issue, so I'm closing this one too. Adding to my previous reply, this is a known issue with Unity - there is no single source of NuGet packages for a project, so each plugin brings its own DLLs which causes conflicts. The best solution as of now would be OpenUPM bringing over some of the most popular NuGet packages to its platform. It is planned <openupm/openupm#553>. While it is not supported, I could reference a package like this <https://openupm.com/packages/com.worldreaver.systemmemory/> instead of bringing in my own DLLs. However, there is a couple of issues associated with it: 1. I haven't seen anyone else use these packages, so it will be necessary to convince other plugin developers to reference them. 2. There are installation issues <https://github.com/worldreaver/SystemMemory/issues/1> in some of the packages, and the author hasn't resolved them yet. In this situation, I prefer to keep it as is, and once OpenUPM starts supporting NuGet packages officially, I will switch to dependencies instead of built-in DLLs. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF5GSVQELOGGWQPNPRQKL6LS7KYQDANCNFSM4XAXIN5Q> .