SBarnes wrote: is that because Jiwa is using some sort of application assembly resolver to ensure that crystal will works?
No, we don't use a custom assembly resolver in order to locate the Crystal assemblies - our custom resolver is only there for plugin assemblies to be able to locate Jiwa assemblies (as plugins are loaded from the ProgramData folder).
We just use the Crystal installation MSI package in our own installer, which installs Crystal to the GAC and our application references the assemblies in the GAC. The Crystal MSI adds registry entries which are essential for Crystal to work - you cannot just copy Crystal assemblies - and that's the reason why we had to remove support for Azure App Service hosting the Jiwa REST API - even loading a Crystal assembly will fail if those registry entries are not present.
I don't know why there are Crystal assemblies in the Jiwa directory - that could be a mistake... I've checked and we definitely use the GAC assemblies and copy local is false for those references to Crystal assemblies.