What are the files you should not check into source control for a new ASP.net project?
Question
There is a new ASP.Net project in your company/team, be it web form or MVC. Someone have to create it first. So John Doe created it.
- What are the files that John should not check into version control? sln? proj? Anything else?
- If John do not check in sln or proj, how should the rest of the team open the project after they check out from version control for the first time?
1 answers
solution1
2 2016-06-06 09:50:04
You should check in .sln and .proj files.
Some of the files/folders which you typically do not check in are:
-
*.suo -
*.user -
packagesfolder -
binandobjfolders - typically, any folder starting with a dot, eg
.vs -
node_modules
Depending on the project type, there will certainly be more files/folders which are typically not kept under version control.
BTW: see also this question: Should I add the Visual Studio .suo and .user files to source control?
The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.
Related Question
What ASP.NET MVC project files should be kept in a repository?
What files do you check-in to source countrol management system when working in an ASP.NET web application?
Should project.lock.json file be checked into source control? (ASP.NET Core 1.0)
Clarifying `.dll.refresh` files, source control, and build of an asp.net web site project
write source files to output in custom asp.net server control
What ASP.NET MVC project files should I not add to Subversion
ASP.NET MVC 2 project default script files. What do you use?
What should you be storing with an ASP.NET Profile Provider?
If an asp.net control's event's aren't binding, what are the things I should check, in order of likly cause?
New ASP.NET project
Related Tags