Two fixes for resolving paths on Unix-like systems:
1. Use Path.DirectorySeparatorChar instead of “\” when assigning BaseDirectory and OutputDirectory.
2. It’s possible that dnlib could provide the location of a module as a path relative to the current directory (in my observation).  Since Utils.GetRelativePath throws an exception when “filespec” is a relative path, the parameter must be made into an absolute path first.
Don’t rename virtual methods which implement an interface method or override a method declared in a base type, when the interface or base type is declared in an assembly that is not currently being processed.
Fix injection version and a mistake from pull request