Replies: 2 comments 2 replies
-
Hello! All assemblies from that script are used by Unity. So we cannot create an assembly with any of these names because in such case TriInspector will conflict with one of the standard libraries. And it will be impossible to fix it since the project cannot have two assemblies with the same name. Instead, the TriInspector uses a asmref to the internal bridge assembly from the DOTS package. If the project does not use DOTS then you need to run the installer ( https://github.com/codewriter-packages/Tri-Inspector#how-to-install ) that will create missing asmdef. |
Beta Was this translation helpful? Give feedback.
-
Thank you really much @vanifatovvlad for the discussion and for the explenation, now I understand the reasons and the context. |
Beta Was this translation helpful? Give feedback.
-
Hi @vanifatovvlad,
first of all I want to say that this is a awesome well enginered Package.
It came to my attention that currently Tri-Inspector is referencing Unity.InternalAPIEditorBridge.012 from another packages by name.
I think currently it is from DOTS package?
If non package is available which does include such a assembly it does not work by itself.
Therefore I would suggest to define one assembly itself and take one assembly definition name where internals are exposed to.
The list to which externals are exposed to can be seen here: https://github.com/Unity-Technologies/UnityCsReference/blob/master/Editor/Mono/AssemblyInfo/AssemblyInfo.cs
Why I am mentioning it here and not providing a merge request is, because I would like to here what you think about it and what reason the current state could have.
Beta Was this translation helpful? Give feedback.
All reactions