VS Code: Use current project for build and simulator?

When I'm working with two projects (current release and a test version), I cant switch between projects for build and simulator.

Every time only the first used project is used for the build since VS code was started. Open a new mc file and start build or simulator doesn't work. VS Code is starting the other project again, not the currently opened file.

If VS Code is closed and restarted, I can use the other project. But only this one. For every switch between projects I have to close and restart VS Code.

Ist this a bug or are settings missing in my environment?

0 waterkip over 2 years ago

I dont use VS code, but I think this is where workspaces are for. Have you tried it with that?

0 waterkip over 2 years ago

Just curious, it is the same project/code base and just different release type? Why not use git and branches. You can switch branches and ypu domt need to split it in seperate projects.

0 jim_m_58 over 2 years ago

You can select which project in a work spaces you want to run. Here's a screen shot. You may need to add a new config if it doesn't exits, but here's my workspace with a bunch of projects, and it shows the end of my existing configs and how to add others. You see a config allows running the app or the tests for the app.

0 jim_m_58 over 2 years ago

Also see https://forums.garmin.com/developer/connect-iq/b/news-announcements/posts/moving-from-eclipse-to-visual-studio-code

and the section about launch configs.

0 ronnywinkler over 2 years ago

I used only one workspace yet. But I would like to keep all ConnectIQ related stuff in one workspace.

I will check the lauch config. But for that I have to change between the configs. I read in on of the VS Code documentations (or the FAQ? can't remember where) that the curernt opened file is taken to determine the project what should be used when running the app. That's why I was asking. In the lauch config will be a valid option, that's ok, too.

0 FlowState over 2 years ago in reply to ronnywinkler

ronnywinkler said:
I used only one workspace yet. But I would like to keep all ConnectIQ related stuff in one workspace.

Did you use File > Add Folder to Workspace to add each project (beyond the first one)?

Command Palette > Monkey C: Build Project should build the project associated with the currently opened file, regardless of the existence of a launch.config, in my experience.

ronnywinkler said:
I will check the lauch config. But for that I have to change between the configs.

Actually, you don't. Once you create a launch config for a project, the Run command will work properly when any file in that project is open.

EDIT: I might be wrong about that. I could've sworn this used to work for me. Sorry for the noise.

0 jim_m_58 over 2 years ago in reply to ronnywinkler

In my CIQ workspace I have 20+ projects, and the pics I posted show how I can select any of them. Then in the run menu, I select with or without the debugger and the run config I selected runs.

0 ronnywinkler over 2 years ago

FlowState said:
Did you use File > Add Folder to Workspace to add each project (beyond the first one)?

Command Palette > Monkey C: Build Project should build the project associated with the currently opened file, regardless of the existence of a launch.config, in my experience.

Yes, exactly this way. One workspace with several added folders. On the first run, it's ok. But the second try with a mc file from another folder, the code from the foirst folder is executed.

0 ronnywinkler over 2 years ago

jim_m_58 said:
In my CIQ workspace I have 20+ projects, and the pics I posted show how I can select any of them. Then in the run menu, I select with or without the debugger and the run config I selected runs.

I created the configs now and can select one of the settings.
But I have to switch there if I want to run an app from another folder? Or is your VS Code switching automaticalle to this setting/folder if you opened a mc file and hit Strg+F5?