Vex VSCode Extension does not recognized a project created thorugh the vscode extention

VEX V5 Technical Support
1

I could not find the proper channel to post this question.
We are evaluating the vex vscode extension and stumbled upon this issue.

When the project is migrated from V5 pro, we can open the project by clicking import project since there is V5pro project file to choose

However, we found that a new project created from the vscode extension, it does not recognize the project and no vex build button shows up at all.

It is especially a problem when the project is shared via Github.
We tried to change the home directory to point to the github project folder but we couldn’t find the way to open the project or make it recognize the project so that we can see the vex build buttons.

Could anyone clarify how the vscode extension decides whether to show the build button? I wonder whether we missed any autogenerated file in the project.

We noticed that the new project only recognized (showing the vex build button and other buttons in the bottom tray) by the vscode vex extension only after creating the project and when opening from the original location.

2

The build button will only be displayed if a valid VEX Extension project is detected.
A valid VEX Extension project includes a vex_project_settings.json file in the .vscode folder of your project directory.

Could you submit an issue using the VEX Feedback Extension.
image

Then I can take a look at the logs and see what’s going on.

3

make sure you don’t have a .gitignore file that stops the .vscode folder from being commited. VEXcode V5 Pro may have created that entry as five years ago when we wrote V5 Pro it was thought to be a good idea.

4

I actually added a .vscode folder from the project since it is user specific settings that should only hold data that can be regenerated for different devs.
It is quite known practice (visual studio code - Should I commit the .vscode folder to source control? - Stack Overflow)

Does vscode extension for vex rely on .vscode folder to determine whether the project is valid or not?

The problem with .vscode is that it could also include OS-specific (mac vs windows) configuration as well which might not apply to other team members.

Could you confirm which file in .vscode the vex vscode extension use for the project validity check?

5

These files are all used as part of a VEX extension project.

image
image728Ă—264 20.9 KB

6

Thank you for your confirmation.

My only concern is whether the extension stores the OS specific ( path to the compiler) and user specific data (location of the project) in that.
These information will vary by each people and OS. This will limit the sharability of the project via github.

Could you confirm that?

7

I wonder also whether the extension update the files in .vscode if some of the data is not compatible (sdk installation path etc).
If so, it will be ok to share .vscode.

8

pretty sure that c_cpp_properties.json and settings.json will be recreated or updated if they are removed or move between Mac/Windows. vex_project_settings.json does not have any OS specific information, you can probably just commit that one file.

1 Like
9

That’s perfect. We might want to have that in our documentation.

10

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.