DLL makes error when they are on a package but not on asset folder

Unity Engine
, , , , ,
1

Hello everybody,

I have a strange behaviour on Unity 2022.3.5f1.
I have a custom package retrieved by the unity package manager on a custom registry.
This package contains various DLL (with theirs meta file) I’m using.
Since my update to 2022 from 2020 theses dll are ignored because of some “error”:

Assembly ‘Packages/ch.lhs.ocf.unity/lib/System.Printing.dll’ will not be loaded due to errors:
System.Printing references itself.

When I remove the dependency to this package on the manifest.json and I copy all dll and metas from the package cache to the Asset folder, it works fine.
NB:Validate reference" are unchecked for all dll in every situation.

Why the editor behave differently with DLL from a package than when they are on the Asset folder?
Did anyone has a clue ?

Thank you guy for your time, I appreciate it.

2

We’re on 2022.3.40f1 by now. Please upgrade, especially since you’re using one of the early patch releases. Those tend to be rather buggy.

With a bit of luck the error goes away. This seems to be one of those fringe cases. You may want to create a new project and pull just that package in to see if the same issue occurs. If not, it may be a project specific issue. You should also try different ways of adding the package, like “add from disk” (pull the repository to some folder) or manually copying it into /Packages to make it an “embedded” package.

3

Thank you for your answer.
You were right, the lasted 2022.3.40f1 version fixed this issue. I’m sorry to not try to update before asking for help.
Anyway thank you again !