I found these very useful. I could build a .prg with the command line tools, with whatever options I wanted, and then have a launch config setup to run it under the debugger. But now those fields are ignored (and I can see they've been removed from the latest package.json in the extension).
One reason I want to build with the command line tools is that, for example, there's no clean way (that I know of) to setup two build tasks, one which builds debug, and one which builds release. I can set monkeyC.compilerOptions to "-r", but that changes .vscode/settings.json, which is under source control, and I'd like to be able to switch from one to the other without "dirtying" the project. My solution is to setup a normal build task for debug mode, and a task that invokes the compiler directly for release mode, and creates a <project>-release.prg. Then I have two launch configs, one that sets prg/prgDebugXml to the default values, and one which adds the "-release". I have a similar issue with wanting to build from different jungle files (I have my reasons).
I've tried changing the release-build task to just generate <project>.prg, but that doesn't work because after running my build task, running the launch task always triggers a re-build, which then overwrites my release build (I haven't figured out exactly why it thinks it needs to re-run the build).
If these options have gone for good, would it be possible to add a "compilerOptions" field to the monkeyc build task? Or even a "noRebuild" option to the monkeyc launch config?
