The Stonefox

Results 93 comments of The Stonefox

I don't like this idea. I feel it is peppering the scripts with unnecessary helpers. Perhaps there's some other clever way of doing this though? some sort of editor script...

## Workaround ## If you install the Tilia packages before installing any other package that uses the Unity version of Mono Cecil then it works as expected. * Update `Packages/manifest.json`...

Another way of recreating is: * Create a new Unity project in 2020.2.7f1 or above * Add `"com.unity.nuget.mono-cecil": "1.10.1"` to `Packages/manifest.json` * Let Unity install Mono-Cecil package * Update `Packages/manifest.json`...

I've raised a BountySource for this one as it's beyond me https://app.bountysource.com/issues/106260245-infinite-loop-on-import-into-unity-if-another-version-of-mono-cecil-is-already-included-in-project

### Steps for building against a local copy of Malimbe * Git clone the Malimbe repo to a local drive `git clone https://github.com/ExtendRealityLtd/Malimbe.git` * Open `Sources/Malimbe.sln` in Visual Studio to...

I've raised a bug with Unity on this issue as well just on the off chance its an issue with Unity and not a problem with Malimbe 🤞

Not sure if its possible to pack the FodyHelpers and it's version of Mono.Cecil away so it doesn't create a clash using something like: https://github.com/peters/ILRepack.MSBuild.Task I have tried this but...

@bddckr I know you don't have the time these days, but I'm totally stumped on this one. I've tried everything within my limited knowledge to try get it to work...

Stackoverflow post: https://stackoverflow.com/questions/71613966/unity-errors-when-two-packages-that-use-mono-cecil-are-imported

A potential solution I think could be to merge the Mono Cecil dlls into the relevant dlls that rely upon it, then technically Mono Cecil won't need to be included...