Share via

What's in a name?

  • Article

You might have noticed I'm using the executable name “h” in my samples. This is the working name for our command line executable, and it's a short version of “Hatteras”. We don't have a final name for the executable yet. I've gotten accustomed to typing “h”, so I hope the final name isn't something like “VSTSSCC.exe” :)

Anyone have suggestions for a cmd line executable name?

Comments

  • Anonymous
    July 12, 2004
    If you rename it 'j' you're one step closer to being a coder's best friend, because although 'h' is short you have to move your right index away from the home position :)
  • Anonymous
    July 12, 2004
    The comment has been removed
  • Anonymous
    July 12, 2004
    S(ource)C(ontrol)A(pplication)

    and pronounce it [sk?] like i would pronounce in Italian language

    :) Luke
  • Anonymous
    July 12, 2004
    ts.exe
  • Anonymous
    July 12, 2004
    "vault", "sc", "scc"
  • Anonymous
    July 12, 2004
    sourceREALLYsafe? (as opposed to the not so safe, lets corrupt your tree, SourceSafe <g>)

    Whatever it is, just make sure you get the SDC Build Tools guys to add support for it in their MSBuild extensions.
  • Anonymous
    July 12, 2004
    Since I'm guessing that VSTS's source control is at least in part based on Product Studio and Source Depot, why not just use "sd." That way, if it's command-compatible with Source Depot, you can actually drop it into some other teams existing auto-build scripts and the like and have a wider test harness base.
  • Anonymous
    July 12, 2004
    hate.exe for obvious reason
    ha.exe

    dont like hr.exe since it sounds like human resource
  • Anonymous
    July 12, 2004
    CommandLineToolThatDoesNotHaveARealNameYetButWeAreWorkingOnIt~1stVersionBuildInsertBuildNumberHere.exe

    WM_<G>
    thomas woelfer
  • Anonymous
    July 12, 2004
    Well, call it 'I' on days you feel egoistic, and 'U' on days you feel altruistic... :-)

    But more seriously, I guess you want a name that doesn't have too many letters, but more than one. How about 'it' 'the', if you want to use valid english words? You will not be able to turn those into Registered Trademarks, but so will noone else.
  • Anonymous
    July 12, 2004
    another vote for sc
  • Anonymous
    July 12, 2004
    The comment has been removed
  • Anonymous
    July 12, 2004
    How about "SCM.exe" for "Source Code Manager" (or the legacy "Software Configuration Management" or "Software Configuration Manager") ?
  • Anonymous
    July 12, 2004
    And the server-side could be euphemistically called "SCMS" (SCM Server).
  • Anonymous
    July 12, 2004
    How about SourceUtilityManager(SUM.exe)?
    & for SEERVER-SIDE...
    SourceServerNavigator(SSN.exe) ?!
  • Anonymous
    July 12, 2004
    The comment has been removed
  • Anonymous
    July 13, 2004
    Every time I hear the name of this system it's different - Team System, Team Foundation System, Team System Team Foundation (!), ...

    I'd go for "ts" as the command name, because "Visual Studio Team System" is the variation of the name I hear most commonly and also the one I dislike least ;)

    "tf" is tinyfugue to us old unix MUDers...
  • Anonymous
    July 13, 2004
    While the PS and/or SD connection is an insightful guess, it's not quite accurate.

    There's a lot of (reasonable) conjecture out there that Hatteras is built on the VSS and/or Source Depot codebases.

    This is true, at best, in a "spiritual" sense (Any X-Com fans out there will spot that reference, I think), for Hatteras.

    When the team had tough design decisions to make, VSS and Source Depot were both looked at in the "Well, how did THEY solve this problem?" context. That doesn't mean Hatteras blindly does what they did; just that we to learn from our history and previous experiences, right/wrong, good/bad, different, and everywhere in between.

    But, in general, it would be most accurate to see where Hatteras reuses features, or approaches, and (where VS is concerned), the source code provider interface (and properly so). Assuming we built on the VSS (or SD) codebase may lead to bad assumptions that Hatteras acts a certain way because these products act that way.

    Hopefully, we're only the same as them in the 'good' ways :)
  • Anonymous
    July 13, 2004
    Oh, and while I think "vstssccc.exe" is probably the shortest 'canonical' name (Visual Studio Team System Source Control Client), my current realistic vote is for tfc (team foundation client).

    I'm wary of any name that's generic (like scc), because if every source code control system out there did that, we'd have a big mess, and the exception (standards-implemtations like telnet, ftp) does not apply.
  • Anonymous
    July 13, 2004
    The comment has been removed
  • Anonymous
    August 04, 2004
    Maybe it's already too late, but why not 'tfs.exe'? Since the acronym TFS will be used sall over the place, it seems logical that the utility is named the same way, even though tfc.exe is probably more accurate and even though not all of teh TFS functionality will be accessible via tfs.exe/tfc.exe. (Maybe the other teams can add their functionality to tfs.exe in future versions.)