3.23 Microsoft teamfoundation server seminar

At two o'clock P.M., I attended a Microsoft teamfoundation server seminar with several colleagues at the 18-storey modern automobile building. it took about 12 yuan to get out of the company and take a taxi to the destination. It was similar to the plan, and it was about the same as the bus fare (4 people.

There are not many people attending the meeting, but there are many people on the first floor who do not know what to do. after going up, I got a bag as usual, but this time I did not bring a pen. I was so depressed that I had to borrow a pen from the front-end LADY :(

The meeting started at the agreed time, and was presented by Mr. Jin Yulin, a Microsoft lecturer. the first is the introduction to vsts, which roughly tells you that Microsoft products are very good and different development versions are defined according to different needs, such as Developer Edition and architect edition, tester version and so on. they are all routine introductions and there is nothing new.

The keynote speech will be given in the following parts:
1. teamfoundation Server Analysis
2. Work Items Analysis
3. Team build Analysis
4. Migration of source control and VSS.
5. Summary.

Mr. Jin Yu lin's speech was still very passionate. After three hours, he was still energetic and not easy to understand :)
Next, let's talk about my personal feelings.

Five parts above
I am more careful and interested in the WROK item section, team build, source control
For source control, TFS and VSS are compared here (this is the same root, why is it too urgent)
We can see that VSS is suitable for small teamsSource codeManagement, usually around 5 people, but according to China's national conditions, usually around 20 people
The main problems with VSS are performance (number of concurrent users) and security (the folder sharing method is not secure enough)
TFS claims to support concurrent operations by 50 people and support independent databases (sql2005, and cannot be replaced by other databases, which is a cost ...), in this case, it seems that TFs should replace VSS, Which is exactly Microsoft's idea. Of course, in small team development, VSS will still have a certain market, otherwise MS will not have to launch vss2005 :)
VSS project migration also requires attention, and there are many restrictions in it. There is no way to migrate projects by share or other methods. it seems that there is no good way to solve the problems that may occur during actual migration. It depends on whether Microsoft will release a new migration tool.

I did not mention many details, such as the check-in and check-ou operations in TFs. After multiple users modify the same file, check-in is automatically combined based on whether the modification is the same. If the conflict exists, it is converted to manual processing.

As a whole, this seminar still has some value, at least let me understand some of the principles and advantages of TFS, and also gave it to our project teamCodeManagement, there are more options for project management.

For more information, see the following link:
Http://msdn.microsoft.com/vstudio/teamsystem/
Http://blogs.msdn.com/AskBurton
Chinese materials:
Http://www.microsoft.com/china/msdn/library/langtool/vsts/0504teamsystem.mspx