Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Command line arguments are not loaded from json file. Json file is deleted instead. #173

Open
EricCreusen opened this issue Mar 8, 2024 · 3 comments
Labels

Comments

@EricCreusen
Copy link

I'm trying to save the command line arguments to a json file. In my setup, the solution file is generated by CMake in a build directory. Since this build directory tends to be deleted regularly, I want to save the command line arguments somewhere else.

I use these settings:
image

When I create some command line settings, these are stored nicely in a json file at C:\workspace<Solution Name>.args.json. Opening this json file shows the correct values as well.

However, if I restart visual studio and open the same solution, these values are not loaded. I.e. the command line argument window will be empty. Shortly after opening the solution, the file at C:\workspace<Solution Name>.args.json is deleted. At this point, inputting new command line arguments will create a new .args.json file, which is then also deleted upon restarting.

I'm using Visual Studio 2017.

@Irame
Copy link
Collaborator

Irame commented Mar 15, 2024

Thanks for using our extension and reaching out to us with you problem.
Yes, this was an issue with the latest version. Could you try the latest prerelease v3.0.2 and report back if the issue persists?

@Irame Irame added the bug label Mar 15, 2024
@KirstenWF
Copy link

FYI I am on Version 3.1.0 and still have the above issue

@Irame
Copy link
Collaborator

Irame commented Sep 19, 2024

Hi, version 3.1.0 is the same as 2.6.0.
I had to do this because I needed to roll back the release of 3.0 and the VS Market Place does not allow the removal of a version, so I needed to upload a newer version.

If you want to try the fix use v3.0.3.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants