Conventions for storing Visual C# projects in an SVN repo -


Actually my question is that what you store some parts of C in a repository ? In a year I took the last year, I was told that you do not store files in version control anytime (so if you are typing, do not submit .o / .exe files).

But it's easy with C, because you just have to. You can save C, H. and MessFile, and you can simply check the repo, run a Mac file, and do all the work.

But I'm doing with C # projects in Visual Studio

If I only store .cs files, then it's weird to add them to the project on other computers Do I have to store project files too?

The problem I am running is that I used to store only the entire project directory, but then when I put the project on a separate computer, it will complain that the temporary key is incorrect (.px file ) ...

So what do I need to store?

Thank you.

The way they do it - I am saving everything:

  • bin and the obj solution in the directory of each project
  • .user and .suo files - There are user-specific projects and solution options
  • Researchers are generated files (there is a visual studio extension on the river that creates some files in the solution folder)

    Actually, rule of thumb C. special machine is generated by or a device for storing specific things (a compiler or a Visual Studio extension - like Resharper) in my case.

Comments