I solved a rather hard to debug problem. Since placing our projects on a network drive, the EasyBaml command line tool stopped working and simply showed a "FileNotFound exception" or just an error code.
To allow EasyBAML to access assemblies on network drives (maybe this is only required for newer .NET versions), the following EasyLocBaml.exe.config helps:
I hope this helps anyone facing the same problem!
Btw something unrelated, in EasyLocBaml.cs in line 70 there's a "throw e". It should be a "throw" otherwise the stack trace is discarded. However, this only seems to be relevant for debugging anyway.