Currently you need to add the path to the installed Rhino in the config.xml. This is nice when Rhino is installed in a custom location, but if you want to just target Rhino in the vanilla install locations across platforms, it is redundant. Currently, if we do not set a RhinoSystemDirectory in a config, Rhino.Testing sets the RhinoSystemDir to the calling assembly location: https://github.com/mcneel/Rhino.Testing/blob/rhino-9.x/src/Rhino.Testing/Configs.cs#L89
This should be fixed to allow for omitting the RhinoSystemDirectory in the config xml to let Rhino.Inside.Resolver.Initialize() find Rhino where we have said it should be on vanilla installs.
Currently you need to add the path to the installed Rhino in the config.xml. This is nice when Rhino is installed in a custom location, but if you want to just target Rhino in the vanilla install locations across platforms, it is redundant. Currently, if we do not set a RhinoSystemDirectory in a config, Rhino.Testing sets the RhinoSystemDir to the calling assembly location: https://github.com/mcneel/Rhino.Testing/blob/rhino-9.x/src/Rhino.Testing/Configs.cs#L89
This should be fixed to allow for omitting the RhinoSystemDirectory in the config xml to let Rhino.Inside.Resolver.Initialize() find Rhino where we have said it should be on vanilla installs.