哪些Visual C ++文件类型应提交给版本控制? [英] Which Visual C++ file types should be committed to version control?

问题描述

应将哪种Visual Studio \ Visual C ++文件类型提交给版本控制?
在我的项目中，我具有以下文件类型:

Which Visual Studio \ Visual C++ file types should be committed to version control?
In my project I have the following file types:

aps
cpp
exe
filters
h
ico
idb
ipch
lastbuildstate
lib
log
manifest
obj
pch
pdb
rc
rc2
res
sdf
sln
suo
tlog
txt
user
vcxproj

对于每个简短的推理，我将不胜感激.如果其中任何一个有争议，请注意.为了完整起见，我特意包括了一些琐碎的文件类型.

I would greatly appreciate a short reasoning for each. If any of them are controversial, please note it. I'm intentionally including even trivial file types for completeness.

编辑

一方面，我希望将来独立于平台.另一方面，在不久的将来，我想与具有类似设置的团队成员合作.设置之间的文件夹兼容性当然是一个选项，因此，如果它简化了工作流程，则可以包括保存路径的配置文件.
同样，我当然希望解释什么是正确的.

On one hand I would like to be platform independent in the future. On the other hand in the near future I would like to work with team members with similar setups. Folder compatibility between the setups is certainly an option, so configuration files holding paths may be included if it eases the workflow.
Again, I would surely appreciate an explanation what's what.

推荐答案

是:

• cpp:源代码
• 过滤器:项目文件
• h:源代码
• ico:资源
• rc:资源脚本
• rc2:资源脚本
• sln:项目文件
• txt:项目元素
• vcxproj:项目文件

否:

• aps:上一个资源编辑器状态
• exe:生成结果
• idb:构建状态
• ipch:构建帮助程序
• lastbuildstate:构建助手
• lib:构建结果.可以是第三方
• 日志:构建日志
• 清单:构建帮助器.可以自己写.
• obj:构建助手
• pch:构建帮助器
• pdb:构建结果
• res:构建助手
• sdf:智能感知数据库
• suo:解决方案用户选项
• tlog:构建日志
• 用户:调试设置. 仅保留一个开发人员设置或自定义调试设置

• aps: last resource editor state
• exe: build result
• idb: build state
• ipch: build helper
• lastbuildstate: build helper
• lib: build result. Can be 3rd party
• log: build log
• manifest: build helper. Can be written yourself.
• obj: build helper
• pch: build helper
• pdb: build result
• res: build helper
• sdf: intellisense dbase
• suo: solution user options
• tlog: build log
• user: debug settings. Do preserve if just one dev or custom debug settings

其中的一些很不稳定，因为它们都可以自动生成并自己维护.而且还有更多没有出现在列表中的东西.首先要注意文件的位置.如果它在您的解决方案或项目目录中，那么您很可能希望将其检入.那么在Debug或Release子目录中的可能性就很小. Build + Clean删除了很多噪音文件.当然，还有:签入，重命名项目目录，签出并验证它是否已构建.

Several of these are iffy because they can both be auto-generated and maintained yourself. And there are several more that don't appear in your list. Primarily pay attention to the location of the file. If it is in your solution or project directory then it's highly likely you want to check it in. In the Debug or Release subdirectories then highly unlikely. Build + Clean removes a lot of the noise files. And of course: check-in, rename the project directory, check-out and verify that it builds.

这篇关于哪些Visual C ++文件类型应提交给版本控制?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！