Moq and Castle-Core dependencies

Unity Engine
1

UIToolkit 1.0.0-preview.13 has dependencies to Moq and Castle-Core:

Those dependencies are in conflict with the ones that we use in our project and so opening the project ends with errors like this one:

Unity packages should not have dependencies to those libraries. They are very common and every project should be free to use whichever version they want.

That is actually preventing us from migrating our project to UIToolkit - there is no way we could redo the whole project to use the outdated (2018?) versions of Moq and Castle Core.

2 Likes
2

Well, actually it is fine that that even official unity packages depend on other nuget packages. The problem is that we can’t use the standard .net toolchain, and just resolve the needed version for dependecies…

1 Like
3

@Huszky Totally agree. In the short term though UIToolkit should adhere to the existing convention in other Unity packages and not use such dependencies (or have them repackaged somehow to prevent conflicts with customers’ projects).

1 Like
4

This makes sense, the dependency is used by our unit tests which are not directly part of the package anymore. I’ll see what can be done.

5 Likes
5

@uMathieu Thank you!

1 Like
6

Even if you don’t need the a newer version of Moq, I couldn’t get my tests to point to the package manager’s nuget version of Moq without setting up Assembly Definitions and doing the reference override.

Which is a currently usable workaround, but certainly painful if you don’t have Assembly Definitions already set up.

7

@uMathieu The problem is back again with preview-15.