Search Unity

Bug Additional runtime assemblies are not detected correctly

Discussion in 'Visual Scripting' started by AnsisMalins, Jul 10, 2022.

  1. AnsisMalins

    AnsisMalins

    Joined:
    Mar 16, 2014
    Posts:
    30
    Previously: Bug - Additional editor assemblies are not detected correctly - Unity Forum

    Updating from Visual Scripting 1.7.6 to 1.7.7 got me the opposite problem: all my runtime assemblies that are not Assembly-CSharp, etc. are misdetected as editor assemblies because they depend on UnityEngine.UI which depends on UnityEditor.CoreModule, and 1.7.7 takes assembly references into account, transitively.
     
    AnsisMalins, Jul 10, 2022
    #1

  2. AnsisMalins

    AnsisMalins

    Joined:
    Mar 16, 2014
    Posts:
    30
    It looks like every single asmdef depends on UnityEditor.CoreModule for as long as No Engine References is off.
     
    AnsisMalins, Jul 10, 2022
    #2

  3. AnsisMalins

    AnsisMalins

    Joined:
    Mar 16, 2014
    Posts:
    30
    Never mind, there's 1.7.8 which addresses the issue.
     
    AnsisMalins, Jul 10, 2022
    #3