Visitar URL original
move code depending on UnityEditor into separate assembly by nonemec-havok · Pull Request #1649 · MessagePack-CSharp/MessagePack-CSharp · GitHub
Skip to content

move code depending on UnityEditor into separate assembly - #1649

Merged
AArnott merged 1 commit into
MessagePack-CSharp:masterfrom
nonemec-havok:move-UnityEditor-dependency-into-asmdef
Jun 27, 2023
Merged

AArnott merged 1 commit into
MessagePack-CSharp:masterfrom
nonemec-havok:move-UnityEditor-dependency-into-asmdef

Conversation

@nonemec-havok

Copy link
Copy Markdown
Contributor

VisualScripting has a overzealous protection preventing calls into assemblies that depend directly or indirectly on UnityEditor, even if that code is enclosed in #if UNITY_EDITOR. The most painless workaround is to move that dependency into a separate assembly at some level.

@AArnott AArnott added this to the v2.5 milestone Jun 27, 2023
@AArnott
AArnott merged commit a1a7417 into MessagePack-CSharp:master Jun 27, 2023
@nonemec-havok
nonemec-havok deleted the move-UnityEditor-dependency-into-asmdef branch June 28, 2023 08:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants