Heh-heh, I don't believe so. OTOH, Hanselman, who does work for Microsoft, and who has the freedom to pick his own tools, uses Git. I doubt they use it within the walls of Redmond, however. They should.<s>

Hank

>Yeah, but the guy who wrote it doesn't work for MS, does he? :)
>
>>You will love Git: only deltas, from what you pulled, get saved. Period. Integrates with OnTime and most other Issue/Feature/Help Ticket systems. Git-tfs integrates TFS with git.
>>
>>Hank
>>
>>>>>>He really said that.
>>>>
>>>>I hate to admit it, but I agree with him.
>>>>I've been doing this for decades and I've only seen one or two instances where a version control system might have been worth the effort it takes to buy it, learn it and deal with it day in and day out.
>>>>As I saw it the cost of not having it was far less than the cost of having it.
>>>>I know that there are some very smart people who insist on using it, so I'm probably missing something huge, but my practical nature doesn't let me find out what I've been missing all these years.
>>>
>>>There are very good reasons for version control. We are human. We make mistakes. Being able to revert a mistaken change is wonderful. As with most useful things, they start out really difficult to use.
>>>
>>>I recently "complained" about TFS on MSDN forums. It tracks differences between one version of a file and the next, during submissions, so it knows that out of 1 Gb, only 10 bytes changed.
>>>
>>>It does not use that information to update the files on the other developers' machines. It sends the entire 1 Gb to each of the 10 developers. Maybe not a problem on a high-speed LAN, but it sure feels wrong to me. I view this as the typical case of - "who-cares-if-it-is-slow-itis. Kiss has become to mean Keep It Slow isn't Stupid.
>>>
>>> A Microsoft employee liked my idea, though isn't sure how to implement.