Team Foundation Server - version control: * Storage: SQL * Changesets support - atomic commits (how cool!) * Renames tracking support * "Proxy servers" read/write support! (MSDN should carry some technical info about how it's done. Is TFS a fully distributed VCS?) * Of course very tight integration with Visual Studio * Tight integration with "Microsoft's Bugzilla" (Foundation Server's "work items") - I think many managers will love it, many developers will hate it (also encourages large checkins, it seems) - controlled by "development methodology" (you choose that project-wide) * Support for pre/post-commit hooks (tests: passes compilation, static analysis, ...; email notification) - controlled by "policy" * Optional locking of files against modifications by others * Branching support (and can do merges too, but no details; wasn't covered in detail) * Shelving - formally not a check-in, "named personal shelve of your work in progress on the server" (you can then restore the original version and return to your shelve later) (why don't they just create branches for that?) * Took 2.5 minutes of clicking to get a diff of two versions of a file, you are committing by selecting single menu item from the middle of a loong menu, etc. * Support for both automatic and manual (visual) merges * http://www.codeplex.com/ - sourceforge-like repository for _open-source_ projects developed using TFS * Next week, I should be able to get to try it out in practice :-)