I just attended a TFS "MSDN Briefing" and was shocked that TFS does not support keyword expansion .... So I've asked Dr. Google and found this project and
https://connect.microsoft.com/VisualStudio/feedback/details/192014/support-for-tfs-keyword-expansion (90 votes atm does not convince MS to implement it ... ^^).
So I have a few questions:
- Why does MS not implement that feature for TFS (I assume there is a "good reason" for that)?
- Does this "Keyword Expansion" (aka "Keyword Substitution") project store the expanded keywords into the source file at the repository or does it only do it
locally like Subversion does?
- Does it also work for binary files (e.g. SVN: $keyword:: $ is working fine for .doc, .xls etc.)?
- Does it work for UNICODE files (SVN does not support keyword expansion for Unicode files ...)
- Is there a support for zip-container files formats (e.g. .docx, .xlsx etc. SVN does it not support)
Thanks in advance!
Harald-René Flasch (aka hfrmobile)
Apr 17, 2011 at 12:34 PM
You should ask MS and not me…
The keywords are stored in the source file during check.in and therefor also in the servers database’ file
It does currently not work for binary files. If you know who to do it, I can try to implement it.
It works with any encoding; including Unicode
It does currently not work for zip files. If you know who to do it, I can try to implement it.
thank you for your reply!
- At a MSDN Briefing (Microsoft Austria) about VSS --> TFS they told that this feature is missing but they don't told us why. Maybe even Microsoft employees do not know it ;-)
- The only drawback at the moment (but maybe the only approach so that TFS does not recognize it and diff will work etc.?)
- I would suggest a similar/same approach as SVN does: $keyword::__________$ the
:: has the effect that the number of characters between
$ are always the same. If the expanded text is to short it will be filled with spaces if the expanded text is to long it is limited - this works fine for binary files like MS-Word, MS-Excel etc. since the number of bytes/size of the file is never changed
- This is an advantage (compared to SVN)
- The simplest approach (maybe the only approach?) when committing (checking in) extract it, do the expanding and zip it again) (FYI: .docx and .xlsx are .zip files)