You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SCANsat has an assembly that needs to be included in its unity project, which means that it cannot depend on KSP's Assembly-CSharp. There may be a workaround here by providing a stub dll with the things that it would need (mostly KSPAssembly and KSPAssemblyDependency attributes).
KOS has an assembly that should not depend on Unity nor KSP - the core of the mod is actually a totally pure C# assembly so that it can be unit-tested outside of the game.
In both cases, the assemblies should be compiled by KSPBuildTools just like actual mod assemblies and copied to the binary output directory, etc.
To support these use cases, we should add a mechanism to disable the auto-referencing of the unity and KSP assemblies. Something like:
SCANsat has an assembly that needs to be included in its unity project, which means that it cannot depend on KSP's Assembly-CSharp. There may be a workaround here by providing a stub dll with the things that it would need (mostly KSPAssembly and KSPAssemblyDependency attributes).
KOS has an assembly that should not depend on Unity nor KSP - the core of the mod is actually a totally pure C# assembly so that it can be unit-tested outside of the game.
In both cases, the assemblies should be compiled by KSPBuildTools just like actual mod assemblies and copied to the binary output directory, etc.
To support these use cases, we should add a mechanism to disable the auto-referencing of the unity and KSP assemblies. Something like:
The text was updated successfully, but these errors were encountered: