Issues Addon BINDER - Basic installation

[Agartha-KSP]

Hello!

Would it be possible to ask for a little help please?
I don't know why, but i got 3 ADDON Binder issues in the KSP.log trying to run your ModuleManager :
ADDON BINDER: Cannot resolve assembly: KSPe.UI.14
ADDON BINDER: Cannot resolve assembly: KSPe.KSP.112
ADDON BINDER: Cannot resolve assembly: KSPe.Unity.2019

=> i tried to make a fresh install, but the 3 errors persist. I don't know why, as the .dll are in the right place from what i can understand with my limited understanding.

KSP.log

MMPatch.log

Player.log

[Lisias]

Season's Greetings, @Agartha-KSP .

These ADDON BINDER: Cannot resolve assembly: messages are misleading, IMHO they are a mistake on KSP.

TL;DR: Every time you ask a thingy called Assembly Loader/Resolver if an Assembly is loaded in memory, KSP prints that message in the KSP.log for... reasons. 😝 Every time you see it on the log means only that someone asked the AL/R for the thing - if it is an error or not, it will depend from what the caller code is trying to do.

For example, take this excerpt from your log:

[ERR 23:38:02.541] ADDON BINDER: Cannot resolve assembly: KSPe.Unity.2019

[LOG 23:38:02.542] [KSPe.Binder] Looking for KSPe.Unity.2019.dll on GameData\000_KSPe\Plugins\PluginData\...
[LOG 23:38:02.543] [KSPe.Binder] Found it on C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\000_KSPe\Plugins\P
[LOG 23:38:02.544] [KSPe.Unity2019] Version 2.5.5.1 /L

Since I was the dude the coded KSPe, I know that it verifies the environment and then loads a "subassembly" with tools for that environment. So KSPe detected it was running on Unity 2019, and checked if that Assembly wans't already loaded (just in case), and it's the reason you see the first ADDON BINDER"error" (please note the quotes" message.

Then KSPe askes its internal component for that assembly, this thingy is called KSPe.Binder. This binder prints a message saying that it's looking for that specific Assembly on that specific directory and, if it finds it, prints a message saying where it was found, load the thingy and initializes it. The last message is that Assembly announcing the World it's alive.

You can safey ignore THIS message (the ADDON BINDER thingy) until a Reflection Exception happens (what means, most of the time, that something that should had been loaded wasn't). When you find that kind of Exceptions, then the ADDON BINDER messages will guide you to find who is probably M.I.A., helping on fixing the problem.

O a personal note, this message should not be a ERROR, just a INFO, and instead of saying "cannot resolve", should sat "trying to resolve". On an ideal world, what follows is what KSP should be writing on that log:

[LOG 23:38:02.541] ADDON BINDER: Trying to resolve assembly: KSPe.Unity.2019

[LOG 23:38:02.542] [KSPe.Binder] Looking for KSPe.Unity.2019.dll on GameData\000_KSPe\Plugins\PluginData\...
[LOG 23:38:02.543] [KSPe.Binder] Found it on C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\000_KSPe\Plugins\P
[LOG 23:38:02.544] [KSPe.Unity2019] Version 2.5.5.1 /L

So, don't worry. You are fine.

Cheers!

[Agartha-KSP]

Oh! Thank you for the enlightment!
And merry christmas... (Or whatever celebrations!).
Ps : i love the way you spell thing in english.