构建操作会导致项目解决方案中出现哪些新的签出
VS 2005 中的某些问题导致项目文件的另一个解决方案中出现新的签出。想象一下，VS 2005（.net 2.0 和 c# ）的一个项目中有 20 个解决方案，
项目名称是： A 、 B 、 C ... S、T，
A 有一些来自 B 或 S 的引用...
当我构建解决方案A，它开始向我签出来自不同解决方案的一些文件（它可能是解决方案文件或项目文件..）
两天前它没有发生过..只有我更改的文件是正常的正在为我办理退房手续。不是其他人。
我应该去哪里检查以使其与在 TFS 上完美构建时使用的相同？
There is something in VS 2005 causing the new check-outs in another solutions of project file. Imagine There are 20 solutions in a Project of VS 2005 (.net 2.0 and c# )
Project names are: A , B , C ... S, T,
A has some references from B or S...
And when I build the solution A, it starts to check-out on me some of files from different solutions ( it may be a solution file or project file..)
It did not use to happen two days ago.. It was normal only the files that I change are check-out to me. not others.
Where should I go and check to make it the same as it use to build perfectly on TFS?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您能否确认只是您的工作环境出现了问题？我曾多次遇到 VS 强迫我签出文件而不是我想要的情况。几乎在每种情况下，最终都会有一个开发人员安装 SP 并更新项目文件，而所有其他开发人员都在不同的 SP 上。
您在这里的另一个选择是关闭此自动结账功能这里有一个演练
当然，这可能不是一个理想的解决方案，但它会在短期内解决问题。我会对项目文件进行比较，看看发生了什么变化。
希望这些想法能帮助您避免皱眉。
Can you verify it is just your working environment that is having the issue? I have ran into many times when VS will force me to checkout files without my wanting it to happen. In almost every case it ended up being that one developer installed a SP and updated the project files while all other developers were on a different SP.
Another option you have here is to turn off this automatic checkout feature here is a walkthrough
Granted, that may not be an ideal solution but it will resolve the problem short-term. I would do a compare on the project files to see what is being changed.
Hopefully these ideas will help you avoid the frown face.