Reply to sender Reply to all Reply to folder Forward Move/Copy Delete Read previous item Read next item Get help information on the current window
From: Lester, Michael  
To: 'Edward Neubecker '; 'Georgios Markakis '; 'Grace Lewis '; 'Julian '; 'Mark Klein '; Lester, Michael; 'Nasari haji '; 'Paulina '; 'thlou '; 'Yue zhao ' 
Cc:  
Subject:  Source Code Versioning 
Sent: 6/10/2002 8:47 PM 
Importance: Normal 

Source Code Versioning inside Microsoft Visual Source Safe

In order to maintain the integrity of our products, version stamps will be placed on each source file so that a configuration baseline can be made of each release.


All source code files will contain header comments that include the following Visual Source Safe keywords in comments:

$Revision: $
$History: $

"Source code" includes the following types of files:   *.txt, *.java, *.c, *.bat, *.cmd, *.xml, *.html, *.pl, *.htm, *.h


Example tags for Java source:
---------------------------------
// Program Name: 
// Date:
// Purpose:
//  -- etc --- See Coding Standard...
// $Revision
/* $History: $

*/

--------------------------------------------------------------------
MSE Studio,

I have enabled keyword expansion in VSS on dogbert for the following
document types:

   *.txt, *.java, *.c, *.bat, *.cmd, *.xml, *.html, *.pl, *.htm, *.h

Please let me know if you need expansion for other types of documents.
Unfortunately, expansion corrupts MS Word documents, so it's not an option.
(I tried it--eats Word files.)  My guess is that it would corrupt other
binary files, too.

What does this mean?  Well, if you are checking in one of these types of
files and you have an embedded keyword (like "$Revision: $" for example),
the keyword will be replaced with a variable from VSS.  This is very useful
for version-stamping source code:  simply include the revision tag within
comment characters.

Attached is a complete list of keywords.  Search VSS help for "keywords" to
produce a more readible list.

Thanks,
Mike


Visual Source Safe Keywords

Type this keyword to add the following:

$Archive: $              VSS archive file location 
$Author: $               User who last changed the file 
$Date: $                 Date and time of last checkin 
$Header: $               Logfile, Revision, Date,Author 
$History: $              File history, VSS format 
$JustDate: $             Date, without the time addendum. 
$Log: $                  File history, RCS format 
$Logfile: $              Same as Archive 
$Modtime: $              Date and time of last modification 
$Revision: $             VSS version number 
$Workfile: $             File name 
$NoKeywords: $           No keyword expansion for all keywords that follow