Description
Currently CLR driver is started by java driver. This is problematic for CLR when for looking for assemblies to load as it would look at %JAVA_HOME%\bin. So we manage our own assembly loading by using AppDomain.AssemblyResolve event. This works but gets us into assembly versioning business. Better to sandwich wrap java with DotNet Driver so that CLR itself can manage assembly loading.