![]() To summarize what files should be ignored in a Visual Studio solution: suo file is the "solution user object" file and should not be added to version control. ![]() sln file defines the solution, and should be committed. Microsoft knew this could potentially be a problem, so they designed a file structure that separates the actual project-specific information from the user-specific information.Īt the solution level, you'll see a. In fact, this very problem is the reason why the. You don't want user-specific files like this in the repository because if you and a teammate have different settings, you'll constantly be overwriting the settings of the other person in the repository. With a user-specific file like this, everyone on a team will have different settings. Instead, this contains information about how you're using the project within Visual Studio, so that when you reopen the project, it can come back in the same state you last left it. This file doesn't contain project specific information. Once you've opened the project in Visual Studio, you'll also probably have a second file called. ![]() For every C# project that you have in Visual Studio, there will be a. The second category is user-specific files. These two both contain compiled files, and you can safely ignore both of these. In Visual Studio, for each project that you have compiled, there will be an obj and a bin folder. Since these files can be regenerated, it is generally preferable to ignore them and not allow this to happen. This means your repository will get really big, really fast. If a file is in a binary format, then the diff tool does a terrible job at figuring out what changed, and the entire binary file (even if it is 50MB) will get committed every time. This is especially the case if the file is in a binary format. These are any files that can be regenerated by other files. Files That Should be IgnoredĬertain types of files can and should be ignored. We'll also cover how to handle a file that was already put into version control that we later decide should be ignored. So in this tutorial, we'll cover what types of files should be ignored, and how to actually ignore them. At every step of the way, Mercurial (and all other version control systems, too, by the way) will keep thinking these are new files that should be added. While we could just simply not ever add them, they'll always be hanging around as files that are new and need to be considered. For these files, it is best to leave them out of version control. There are certain types of files that don't need to go into version control, and in fact, in doing so, often causes more problems than it's worth. I said that we would revisit the purpose of this file a little later on. When we first created a repository, we saw that a file called.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |