All geek questions in one place

Which ASP.NET MVC project files should not be added to Subversion

this is probably a naive question, but I want to do it for the first time.

I have an MVC solution that has the following:

Data project - C# Services project - C# MVC Web Project - ASP.NET MVC Test Project

I am currently using MVC2 source as a means to debug my own code. I do not plan to verify this, but I understand that as soon as I get back to the MVC2 DLL, my decision will change.

I am sure that I just do not need to check the material that changes with each assembly: the bin folder in a web project, for example.

Is there a list of what is not required to manage the source code? :)

+4
source share
3 answers

Exclude the bin folder. Also pay attention to the .user or .suo files. These files save your own settings and will change from user to user, so it should not be in the original control.

If you are using a database stored in the App_Data folder, be sure to ignore it (the database file, not the App_Data folder).

+7
source

As a rule, I exclude the bin and obj folders of each project from the source control. I can’t remember that something needs to be done.

+3
source

Do you use ankhsvn?

I think ankhsvn automatically excludes directories that are not needed in subversion

amuses

+1
source

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

More articles:


All Articles