Add project aliases for weird unity packages - Fix Unity.UI reference for TextMeshPro #98
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Thanks for the change, however, I think we should find a more robust way of making this work. I will look into it, but will leave this open until I find something else. |
Contributor
|
This was essentially brought forward as part of #102, with slight modifications. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have been using Unity 2019.2.17f1 and hit an issue with how TextMeshPro 2.0.0 references Unity.ugui.
Unity.ugui is available in the editor but is not located when generated MSBuildForUnity projects. It seems the Unity.ugui may long term be replaced by UnityEngine.UI, or at least they contain the same class content and references to UnityEngine.UI fix in editor references to Unity.ugui.
When setting up the TextMeshPro reference project (as well as other projects referencing Unity.ugui), redirecting the reference from Unity.ugui to UnityEngine.UI unblocked MSB4U builds outside of the editor. It seems like there may be more cases like this/having the ability to specify a ProjectAliases dictionary may be needed for other UPM packages that are labeled as other items/are available in the editor.