How do you handle VS.net sln and proj files in the source control?

I hope this applies to programming, as it relates to how to structure the project.

Since I always used the website model with VS.net, I never had solution and project files, and everything that fell into the original control worked fine. I knew that everything I had in my website directory was everything I needed for a website.

Now I am using asp.net MVC and I only have a project model, so now I have this solution and project files. If I work on it alone, it’s good, but as soon as other people start adding / removing files from the project, our solution file becomes damaged and people end up having to grab the last solution file, see what has changed, and then add it back / delete their files and check the solution file again. This becomes a problem because sometimes people don’t understand that the solution file has been changed, they make other changes, and then when they check that all other people are updating their files, they find that their files have left the project (although all still physically on the disk).

This is normal? Is there a way to structure the project so that we do not need to check the solution and project files?

+3
source share
6 answers

I do not think this is normal - what do you use to control the source? It seems that the developers do not respect the changes that others make - checking, not merging in the first place.

, , , , - , , , . , - , "" , , .

, , , , , script, .

, .

+2

TFS . , , . TFS , .

, , . , , . , .

[edit] , , *.sln, "Add Solution to Source Control".

+3

, , TFS. , VSS TFS, VSS . - , :

  • ( , , )
  • , , , .

, buidl \out.

, , .

+2

, () . (.sln,. * Proj) , . , .

( , ), .

() , . . / ( ).

, TFS, - . - , .

, - , , ( ) .

+2

, TFS, , ( ), , sln csproj .

, , , , . , / /, , , .

, , , sln proj .

+2
source

Always check them out.

Always check for the latest (if possible merging), make sure that you have a change before checking for a new version.

If your source of control does not require a special action for verification from the old version, GET DIFFERENT SOURCE MANAGEMENT.

0
source

Source: https://habr.com/ru/post/1707721/


All Articles