survey: Multi version support implementation

[aoirint]

I was aiming to enable static compatibility checks against v56 by introducing this setup, but it turned out that NuGet does not support this approach due to technical limitations. As a result, adding multiple versioned dependency definitions (e.g., for v56) would trigger a NU1504 warning ( https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1504 ) during restore/build.

It seems that avoiding this would require moving away from NuGet and managing the DLLs manually as local references, which would add some complexity to dependency management and automation. I’m currently stuck at this point.

• extern alias support for NuGet package references NuGet/Home#4989
• Referencing multiple package versions within one project with extern aliases NuGet/Home#6693
• ProjectReference alias support for multiple versions of the same package within 1 project NuGet/Home#12400

CruiserJumpPractice.csproj

    <!-- Runtime-provided dependencies -->
    <PackageReference Include="BepInEx.Core" Version="5.4.21" IncludeAssets="compile" />
+
    <PackageReference Include="LethalCompany.GameLibs.Steam" Version="73.0.0-ngd.0" IncludeAssets="compile">
      <Aliases>LethalCompany73</Aliases>
    </PackageReference>
    <PackageReference Include="UnityEngine.Modules" Version="2022.3.62" IncludeAssets="compile">
      <Aliases>UnityEngine73</Aliases>
    </PackageReference>
    <PackageReference Include="Rune580.Mods.LethalCompany.InputUtils" Version="0.7.12" IncludeAssets="compile">
      <Aliases>LethalCompanyInputUtils73</Aliases>
    </PackageReference>

+    <PackageReference Include="LethalCompany.GameLibs.Steam" Version="56.0.1-ngd.0" IncludeAssets="compile">
+      <Aliases>LethalCompany56</Aliases>
+    </PackageReference>
+    <PackageReference Include="UnityEngine.Modules" Version="2022.3.9" IncludeAssets="compile">
+      <Aliases>UnityEngine56</Aliases>
+    </PackageReference>
+    <PackageReference Include="Rune580.Mods.LethalCompany.InputUtils" Version="0.7.7" IncludeAssets="compile">
+      <Aliases>LethalCompanyInputUtils56</Aliases>
+    </PackageReference>

Originally posted by @aoirint in #7 (comment)

[aoirint]

This approach could be a good reference. I initially saw it used in SellMyScrap, so it seemed to be fairly common.

• https://github.com/MakuAureo/HQoL/blob/8192d70c26f5eff58384fba668009dc70cc53d3d/HQoL.csproj#L41

Looking more closely, it seems that HQoL actually references the SellMyScrap implementation.

• https://github.com/MakuAureo/HQoL/blob/8192d70c26f5eff58384fba668009dc70cc53d3d/HQoL.cs#L20

Should we adopt multipath references for Unity.Netcode?

I thought switching just LethalCompany.GameLibs.Steam, UnityEngine.Modules, and Rune580.Mods.LethalCompany.InputUtils would be sufficient.

My goal is only to perform static compatibility checks for multiple base game versions.