Relative path for the project dictionary

[RGreg]

Is there a way to make the project dictionary VI Analyzer uses into a relative path?  We are developing a default analyzer configuration file, and one of the ideas my guys had was to save the project dictionary with each project in Git - different projects have different "valid words".  However, we saw no easy way to make it into a relative path (first image).  I have tried playing around with the XML in the viancfg file, but I don't really know enough about it to jury-rig something (2nd image).  Any suggestions are much appreciated.

[Darren]

Easiest thing would be to put the project-specific dictionary in the same folder as the .viancfg file. Configuration paths inside the .viancfg are stored relative to itself, so as long as the project dictionary txt file and the .viancfg file don't move relative to each other, you should be fine.

[RGreg]

What I had in mind was a generalized viancfg file that any developer working on any project could use on a semi-regular basis.  That config file could reference the "project dictionary.txt" dictionary file, and the analyzer would recognize it as the same thing regardless of project.  it sounds like you are saying this idea would work as long as developers take the extra step of copying our standardized config file into the project directory (assuming it is in the same subfolder as the dictionary).  I suppose that might work.