Activity overview
Latest activity by core24
Well, after some head-banging-on-wall (translation: lots of black-box testing and trial & error) I came across the root cause of both issues: my command-line utility arguments were being interpreted by Reflector as reflector command-line arguments even when just calling the API. Of course the code is obfuscated and hidden so I couldn't see exactly what was going on.
For future reference: any -f: or /f: argument is interpreted by Reflector as specifying a different font. That caused the invalid font errors.
And, -s: or /s: arguments are okay -- so long as there aren't more than one on the command-line. If there are, you will get a series of exceptions loading the AssemblyManager(), ending in a fatal TargetInvocationException.
Once I changed both of these to different argument letters (/a: and /p: respectively), all problems went away.
Additionally, the behaviour where running the tool while the GUI was running no longer causes any issues either. There is some hidden, internal argument parsing magic going on that would be nice to have documented... / comments
Well, after some head-banging-on-wall (translation: lots of black-box testing and trial & error) I came across the root cause of both issues: my command-line utility arguments were being interpre...
Red-Gate reflector has problems when used for the API
I've got a tool that is using the Reflector API by adding the reflector.exe as an assembly reference.
I upgraded to the red-gate one because the last lutz version was throwing up the stupid out of ...