VeriStand version control strategies

[_pepper]

I have a VeriStand project that is part of a development test stand, in which we are occasionally adding/changing capabilities.  I would like to maintain some kind of version control on the project, so that I know what the system configuration was and can revert back if needed.  I figured it was just as simple as copying all of the project files to a new folder and changing the name (I have the version in the project name), but it doesn't seem to be working real well.  I don't want to get too far down a path and find out I've messed something up, so wanted to see if anyone else has developed a good method for versioning a VS project.

Also, am I correct that each time you deploy a different project, you have to remove and reinstall the VeriStand Engine in MAX?

[santo_13]

You need to adopt a source code control strategy like SVN, Git etc.,

Are you familiar with any SCC tools, or do any other teams in your company use SCC?

Typically, organizations have standard SCC tools like Git that teams can leverage to standardize processes.

[_pepper]

I do know our software team uses Git to manage code, and I'm familiar with O365 for version control of MS Office files. We also have a PDM system (Enovia) for version control and releasing of formal documents/CAD/engineering data, but it wouldn't work real cleanly for what I'm trying to do.  I'm not familiar with using SCC for other files/packages like a Labview or VeriStand project.  Sound like that is possible, though?

[thumble]

Hi,

we used SVN for older projets and now GIT.

You don't have to reinstall the engine, since there was a crash or you've deployed something else (like à LabVIEW-RT project) on the target.

HAGD