VS Code Export Naming Query

I have a VS Code Project with multiple sub projects as they all share common base class code and some resources. When I export the sub project they are always named with the name of the parent project. Is it possible to control this somehow so that the output file so it takes its name from the sub project name? Otherwise when I export all the projects they overwrite each other.

FlowState over 2 years ago in reply to Robert

Robert said:
When I select "Monkey C: Export Project" from the Command Palette it offers me no selection of which project to export. Is there a way to select which of the Project\Folder to use for the export?

To be clear, for any project-specific command palette actions (like build or export):

- If there's no active project (you just opened VS Code and you haven't selected a project-specific file), you will be prompted to select a project. Subsequent actions will use this project by default. (You won't be prompted again.)

- If the currently active editor contains a project file, this project will be used for project-specific actions, as Jim said

- You don't have to right-click on an editor window at any point. Just select a file from the desired project and open the command palette any way you want. You may find it faster just to press CTRL/CMD-SHIFT-P

Robert over 2 years ago in reply to FlowState

Thanks, I think I have it all working now and integrated to GitHub. I have not needed to use Symlinking of files and my setup is using barrels and a base class project to share/re-use code across the child folders. I can't see a reason to symlink files but maybe your needs are different to mine.

FlowState over 2 years ago in reply to Robert

Cool. Yeah, symlinks aren't really necessary if you always load all your folders and you manually override the jungle files in Monkey C settings.