Importance of configuring servers, SVN vs VSS

Today, I suddenly received a notification from the head that H should be updated to the new LCD driver. After I got the machine, I began to search for the LCD Driver I debugged on the hard disk. I suddenly found something wrong. Zhang has left the company. The driver was put on his computer because it was useless. Later, he thought about it. The computer has been formatted and cannot be found. The data manual is ready for re-debugging. After several hours, there are still some problems. We have to continue tomorrow, which is a waste of time.

Once again, I realized the importance of configuring the server. The stuff developed by an employee only belongs to him before being uploaded. When a person leaves, or the computer breaks down, the stuff does not exist. In the future, you must output your work to the server at any time. It is good for everyone to reflect his work.

When it comes to server configuration, let's talk about SVN and VSS.

VSS, which has been used in the past, must be changed to SVN recently. The leaders said they should change it. I don't know why.

I personally think that VSS is suitable for the development of this small team. I may not have realized its advantages if I find SVN inconvenient.

Here are several items to list. I hope you can give me some advice.

1. save files from the server. SVN needs to rename the file by itself. The file name on the server cannot be used by default, which is prone to errors, when you accidentally save the file, it is not the same as what you need. In most cases, we still need to name the original file name and repeat it by ourselves. I cannot figure out why it is so inconvenient. VSS does not exist.

Copy the checkout folder. This is annoying. Where to copy it, it will automatically associate it with the server. In case of misoperations, it will be restored manually. In addition, because we develop several products at the same time, most of themCodeIt is the same. Generally, the code of a product is first developed and then synchronized to another product.

After SVN is used, if you copy the entire folder to overwrite the directories of other products, it will be a major error. This folder should be linked to the original product directory, now it becomes another directory backup of the first product. It is really intolerable. VSS won't.

Comparison between server code and local code. SVN compares the Code with the comparison tool it comes with. It also makes the code of both the left and right windows completely the same, and then marks it with the color, the color indicates whether the code is updated on the server or locally. Easy to see. VSS, and the left and right windows are different and clear.

4. View logs. SVN logs do not seem to have the ability to automatically generate reports. You need to copy the logs at. Why are you so troublesome? On VSS, you only need to select and save the logs, which is so convenient. Cannot figure it out

5. Overwrite local code. Sometimes, the local file is modified or some debugging code is added. Later, I want to directly overwrite the local file on the server, only 1.1 points can be used to solve unnecessary conflict. Who will tell me why? VSS is born for you, so convenient

 

Sleepy, ready to go to bed, not the disadvantage of SVN first.

Maybe you can modify a file at the same time, which is an advantage of SVN, But it seems useless for us.

In addition, you do not need to log on to the server as VSS at startup every day. SVN can be operated in the local directory.

Sleep. The advantages of SVN are still difficult.