ThunderKit Plugin (assembly definition) setup with System.Reflection.Emit.Label

[Sessional]

I have a ThunderKit project for aloft. One of the parts of that project includes a plugin, AloftModLoader. That mod loader is doing some transpiles (via harmony) to rewrite a few of the methods in the game to make the plugin work the way it needs to.

As a part of that transpile, it's using a Label class from System.Reflection.Emit. However, the project is incredibly moody when building and spits out a few related errors. It appears that these errors are because the AloftModLoader is hitting a few references to the engine. I appear to be able to fix them by changing Unity to target .NET Framework instead of .NET Standard 2.1. I also appear to be able to resolve that mismatch by disabling editor references... However, I need at least some of those references for Monobehaviour and GameObject.Instantiate.

error CS7069: Reference to type 'Label' claims it is defined in 'mscorlib', but it could not be found
error CS1503: Argument 1: cannot convert from 'System.Reflection.Emit.Label [C:\Program Files\Unity\Hub\Editor\2021.3.12f1\Editor\Data\NetStandard\ref\2.1.0\netstandard.dll]' to 'System.Reflection.Emit.Label [C:\Program Files\Unity\Hub\Editor\2021.3.12f1\Editor\Data\NetStandard\compat\2.1.0\shims\netfx\mscorlib.dll]'

It doesn't seem like the end of the world to target .NET framework instead of standard, but at the same time it seems like its artificially reducing compatibility for something that I would imagine should not have to be reduced. Is there some recommendations or insight into the way to set these up? I REALLY like the ThunderKit workflow (aside from the asset staging bundle file being janky), and I would rather keep that mod loader as part of the projects rather than having it as a standalone library floating outside of ThunderKit. My dependency tree would look like this: AloftModFramework (Thunderkit) -> Aloft Mod Loader (external) -> Other Plugins (Thunderkit). And that flow seems worse than I'd care to imagine (already tried it once and it's got lots of little needles).

--

TLDR: how should I include/set up a plugin (assembly definition) that needs System.Reflection.Emit into a ThunderKit project without erroring out for System.Reflection.Emit.Label not being convertable when Unity is targeting .NET Standard 2.1 (or should it just not target that?).

[PassivePicasso]

a couple things, .NET Framework is a larger framework than .NET Standard 2.1.
.NET Standard 2.1 is more portable, but to achieve that it has less stuff in it.

That said, the framework you should target should match the framework the game uses. When importing the game with ThunderKit, I believe that should get set automatically (I'm a bit rusty on this bit, so I'm not really sure that it is truly reliable)

If you can confirm the game targets .NET Framework, then that is what you should use to keep your code aligned with the game.

[Sessional]

So looks like the game maybe targets .net standard 2.1 (is that what msil is in dotpeek?) and BepInEx is maybe my problem since it targets .Net Framework 3.5? And because of this Label pulled in via UnityEngine is conflicting with the Label pulled in via Harmony here because it's .NET 3.5?