Version control of guidance files

Topics: Developer Forum, Project Management Forum, User Forum
Apr 24, 2007 at 9:23 PM
Edited Apr 24, 2007 at 9:24 PM
We are looking into using Guidance explorer for our team to create and maintain guidance and other documentation that historically existed in various sources (emails, word docs, etc.) and help us centralize and distribute the information across a wider distributed team.

We would like, however to maintain some control and versioning of the documentation and I am wondering if there is a prescribed or suggested way to use some sort of version control (ideally TFS) to manage/maintain versions of guidance as it is built.

How is this managed for the Patterns & Practices guidance (particularly given that the ASP.NET guidance and Security Guidance and Team System guidance, etc. are (I assume) built and contributed by a wide collection of individuals?
Sep 6, 2007 at 10:58 PM
Good question. There is not versioning built into Guidance Explorer content at this point, though we've talked about it in the past. For now you could place the underlying xml files under version control. There is one xml file per guidance item, so the granularity works well.

If you strongly want versioning of the content in GE, then add an issue to the issue tracking tab and we'll consider it for a future release.