VS Code plugin can run the wrong PRG file if multiple PRGs exist in the bin/ directory

For transparency I'm posting this here although I've already opened a bug report:

forums.garmin.com/.../vs-code-plugin-can-run-the-wrong-prg-file-if-multiple-prgs-exist-in-the-bin-directory

TL;DR, if you have multiple PRGs in your bin/ directory, the Monkey C plugin will run the first one (in alphabetical order), not the actual PRG that belongs to your project.

This can cause problems if you copy a project that's already been built to use as a base for a new project. Seems like it would also cause a problem if a project folder is renamed.

I also wanted to post this here because someone had posted before about copying a project and seeing the wrong app run.

DaveBrillhart over 1 year ago

Flow State - since I've recently transitioned to VSC, I've seen this. What I do now, which works (but might not be the best way), is tap the Run&Debug triangle icon on the left. Then select from the pulldown the "Run App" for the app I want to be active. Takes just a couple seconds to do that. That seems to inform VSC about the current app I want active, for running and exporting.

FlowState over 1 year ago in reply to DaveBrillhart

Thanks, but I wasn't referring to the known issue with selecting a project to run in a multi-project workspace, which I think we already discussed elsewhere (I'm pretty sure I'm one of the ones who answered that question for you, and pointed out how to create the run configurations that you're referring to.)

I was talking about a problem that occurs if you have multiple PRGs in the bin folder of a single project, which is not an ordinary situation.

Also, this post is 2 years old, the bug it refers to may not even exist anymore.