Mo2 Mode Dev Support

[Noggog]

Mo2 Mode setting has helped end users sidestep Mo2's issues with VFS, but this doesn't address Devs. Solution Patchers always build, as they can't be as certain like Git Patchers that the code hasn't been changed and in need of a rebuild.

Also, even if this was achieved, and solution patchers went into Mo2 Mode and didn't rebuild inside Mo2, that doesn't help the dev that wants to run and debug within Mo2 via Visual Studio.

Some thoughts:

1. Solution patchers can at least be upgraded to act like Git Patchers a bit more and not build in Mo2 Mode. Maybe add some warnings that you need to build solution patchers yourself to confirm they have the latest exe to work with.
2. Perhaps some mode where synthesis can start an app from within Mo2, but pause it waiting for input. Idea would be user would do that with the solution patcher, then attach their debugger from Visual Studio running outside Mo2 (does that even work? Hopefully). And then pressing "proceed" in the CLI to start the patcher, now with the debugger attached.

[metacubed]

Is there any documentation on the command-line parameters that Synthesis passes to a patcher?

If you don't want to rely on SetTypicalOpen and other similar configs, what input is required to perform a "real" run on the patcher dll/exe?