Makefile's and SourceControl integration

[j.jemine]

Hello,

We’ve been using VisualGDB for a few months now, and here is some poor interactions with our source control solution (Vault) that we’ve encountered:

• The Makefile is not automatically checked out for edition from the source control when adding / removing a file from the project (or when modifying VisualGDB Makefile Project Properties)
  • The Makefile is not modified
  • When the Makefile is manually checked out, we have to add and remove a dummy file from the project to force the update of the Makefile
• .vgdbsettings files are not automatically added to source control when creating a project
• .vgdbsettings files are not automatically checked out when editing the VisualGDB Project Properties
• It also often happens that VisualGDB creates .bak files from files under source control at some point. Those .bak files are read-only. When VisualGDB attempts to overwrite it with a new .bak file, we get an error because the file is read-only. Suggestion: force the deletion of the .bak file even if it is read-only before writing a new one.

Beside that, we’re delighted with the features of VisualGDB.

[support]

Hi,

Thanks for the feedback, we will investigate the complexity of checking out .vgdbsettings and Makefiles prior to modification and add this feature to either 5.1 or 5.2.

Note that you can disable the creation of the .old files via Tools->Options->VisualGDB->General->Tweaking->Create .old files.

[j.jemine]

Ok thank you !

[support]

No problem!

[Author]

Posts