I have been reading lots of questions regarding whether vcxproj files should be added to source control or not. The consensus seems to be that they should, but when opening the files I noticed that there are a lot of user specific paths contained within.
Seeing as this is a project that is being worked on by a number of people, should I still add it to source control? It seems like it would clash with other peoples' setups.
The filters file (*. vcxproj. filters) is an XML file in MSBuild format that is located in the root project folder. It specifies which file types go into which logical folder in Solution Explorer.
A file with . vcxproj extension is a Microsoft Visual C++ project file that stores the C++ project information. It contains information that is used by the MSBuild project system to compile and build the final output. VCXPROJ of Visual C++ projects is the same as that of CSPROJ for .
vcxproj file by using any text or XML editor. You can view it in Visual Studio by right-clicking on the project in Solution Explorer, choosing Unload project and then choosing Edit Foo. vcxproj.
Of course they need to be added to source control, .vcxproj is the project file. Quoting MSDN:
Project files no longer use the .vcproj file name extension. Visual Studio automatically converts project files that were created by an earlier release of Visual C++ to the format that is used by the current system. For more information about how to manually upgrade a project, see /Upgrade (devenv.exe).
In the current release, the file name extension for a project file is .vcxproj.
The .vcxproj.user files, on the other hand, do not need to be added to source control. The link above describes what each of these files contain as well.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With