SourceSafe Keyword Expansion Template

We use Visual SourceSafe's keyword expansion. Each of our project's source files has (or should if we remember) the following header when we add it to source control.

// TEST.CPP : implementation file
//
/* $Log: /TEST/TEST.CPP $
*/     
This macro inserts the template into .H and .CPP files.

Sub AddSSHeader()
'DESCRIPTION: Insert the source safe keyword expansion comments at the top of source file

 strName = UCase(ActiveDocument.Name)
 pos = Instr(strName, ".")

 if (pos < 1) then
  Exit Sub
 end if
  
 strExt = Mid(strName, pos)

 if (strExt = ".CPP") then
  strDesc = "implementation file"
 else 
  if (strExt = ".H") then
   strDesc = "header file"
  else
   exit sub       
  end if
 end if

 ActiveDocument.Selection.StartOfDocument

 ' Check for existing keyword expansion
 for i = 1 to 20
  ActiveDocument.Selection.SelectLine

 if Instr(ActiveDocument.Selection, "/* $Log:") > 0 then
  MsgBox "File already has keyword expansion."
  exit sub
 end if  

  ActiveDocument.Selection.LineDown
 next

 strFullName = ActiveDocument.FullName
 pos = Instr(strFullName, ":")

 if (pos > 0) then
  strFullName = Mid(strFullName, pos + 1)
 end if

 ActiveDocument.Selection.StartOfDocument
 ActiveDocument.Selection = "// " + strName + " : " + strDesc + vbCrLf 
 ActiveDocument.Selection = "//" + vbCrLf
 ActiveDocument.Selection = "/* $Log: " + UCase(Replace(strFullName, 
 "\", "/")) + " $" + vbCrLf
 ActiveDocument.Selection = "*/" + vbCrLf + vbCrLf

end sub

Date Last Updated: February 3, 1999



Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • Ever-increasing workloads and the challenge of containing costs leave companies conflicted by the need for increased processing capacity while limiting physical expansion. Migration to HP's new generation of increased-density rack-and-blade servers can address growing demands for compute capacity while reducing costly sprawl. Sponsored by: HP and Intel® Xeon® processors Intel, the Intel logo, and Xeon Inside are trademarks of Intel Corporation in the U.S. and/or other countries. HP is the sponsor …

  • It's time high-level executives and IT compliance officers recognize and acknowledge the danger of malicious insiders, an increased attack surface and the potential for breaches caused by employee error or negligence. See why there is extra emphasis on insider threats.

Most Popular Programming Stories

More for Developers

Latest Developer Headlines

RSS Feeds