when we create a unity project it creates 2 Assemblies , one is Assembly-csharp ,and another is Assembly-csharp-player.
the thing is the DLL i created is compiling/its shows available for assembly-csharp-player , so i can use dll functionality but not for assembly-csharp.
and unity uses assembly csharp while compiling scripts …
Any idea why so ???
5 Likes
I have the same question.
1 year and no answer?
Have you checked google about those files? You would be amazed!
https://docs.unity3d.com/Manual/ScriptCompileOrderFolders.html
Since the “-player” suffixed file is not mentioned, I presume something has an asmdef, as explained in the above link, or else the engine has changed since the above documentation (today) reads for 2019.4.
Beyond that, drop the DLLs into a dot-net-peeker and see what’s inside if you’re curious.
Otherwise if there is no actual problem it sounds a little bit like asking why your car has four cylinders instead of three.
Didnt answer the question tho, just rambling.
1 Like
We’re having this same issue. Building for UWP, there are somehow 2 assemblies. We didn’t (intentionally) create the second assembly “Assembly-csharp-player”. Where did this come from? Some scripts are compiling under it and we can’t get references to those. We’ve never seen this happen before, why now? using Unity 2019.3.7f1
Google the assembly name and the first result is this.
1 Like
Already tried that, and it doesn’t work for me. That link says to
I don’t have any option to “cancel the selection of Player projects”. I am using Unity 2019.3.7f1
