The DefaultPathResolver normally assumes that the library is either located in the domain's base dir or the main module's dir (which should usually be the same anyway), but this becomes a problem when Silk is loaded from a different directory. One solution would be to just set the current directory to Silk's directory... or at least that would've been the case if the resolver checked the current directory.

I believe the DefaultPathResolver should also check the directory of its own assembly. Otherwise, it should at the very least check the current directory. This will allow developers to place Silk in directories separate from the exe.