Should *.componentinfo.xml be included in the repository or excluded?
Having said that it appears to encode absolute (not relative) directory paths which means if you share the project and someone else "git clone's" it there's a chance they have not got the DFPs in the same absolute position as the file suggests that might be an issue?
I suppose one test is to commit the stuff without the component.xml, then git clone a copy in a different directory/drive (or even a different PC) then load and build it in AS7. If it builds without error (presumably because the XML is auto-regenerated ?) then the chances are you don't need to version manage the file.
Of course if that means it ends up using "latest" rather than "version N" and the binary that is finally built turns out different that could be considered an issue that argues the other way.
Another experiment I'm tempted to try is simply to delete (or at rename out of the way) a component.xml file for a project then load the solution and see what happens. Does AS7 re-generate a new copy the same as the previous anyway? If so that would be another argument against committing it to the repo.
EDIT: curious result - so I renamed one out of the way then loaded the solution. A new copy was created but only a couple of lines with none of the previous detail? Perhaps it only comes into play if you set the packs to non-default? (ie not the latest)
EDIT2: Oh I see. After renaming the XML and just letting it create a virtually empty replacement, when I go here:
Everything is greyed - I can't set a "different" pack as it no longer lists the current pack. When I delete the new XML and rename the old one back into place then reload the solution I can access once again:
Based on this evidence I would say the XML is *vital* and you must store a copy !!
Thanks clawson - I will include it!
© 2022 Microchip Technology Inc.