将项目添加到 Visual Studio 解决方案，而无需将该项目进入 Perforce
我知道这是可能的，因为我的一个较旧的解决方案文件混合了一些受源代码控制的项目和一些不受源代码控制的项目。
但是我似乎无法使用更新的解决方案重现该配置。每次我将项目添加到解决方案时，它都会获得一个黄色十字，并且在待签入下，该项目被列为新添加的文件。
这是 VS2008 的 Perforce 插件。
我尝试添加一个全新的项目，而不是现有的项目。我尝试过p4 obliterate。我尝试断开并重新连接源代码管理。绑定和解除绑定。
毕竟，每次我尝试添加项目时，它都会出现一个讨厌的黄色小十字。我似乎无法告诉 Perforce 和 VS，虽然我确实希望对大部分解决方案进行源代码控制，但我不希望这个项目文件处于源代码控制之下。
I know this is possible because one of my older solution files has a mix of some projects under source control and some not.
However I can't seem to reproduce that configuration with a newer solution. Every time I add a project to the solution it acquires a yellow cross and under Pending Checkins the project is listed as a Newly added file.
This is with the Perforce plugin for VS2008.
I have tried adding a brand new project, vs an existing project. I have tried p4 obliterate. I have tried disconnecting and reconnecting source control. Binding and unbinding.
After all this, every time I try and add the project it gets a pesky little yellow cross. I can't seem to tell Perforce and VS that, while I do want source control on the majority of the solution, I don't want this one project file under source control.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我现在发现，在一个解决方案下拥有多个项目、一些项目处于源代码控制之下、而其他项目则没有......的方法是避免将解决方案本身置于源代码控制之下。这样我就可以只获取我感兴趣的签入和签出项目，而忽略其余的项目。
事实上，经过仔细检查，这就是我过去解决这个问题的方法（通过混乱、错误或设计，我不记得了）。
I see now that the way to have multiple projects under one solution, some projects under source control, and others not ... is to avoid having the solution itself under source control. That way I get just the projects I'm interested in checked in and out and the rest ignored.
Which, in fact, on closer inspection, is how I've managed (by muddle, mistake or design, I can't remember) to solve this in the past.
在“文件”、“源代码管理”下，进入“绑定”对话框。单击相关项目并解除绑定。您可以将其他项目和解决方案本身保留在源代码管理中。
Under File, Source Control, go into the Bindings dialog. Click the project in question and unbind it. You can leave the other projects, and the solution itself, bound to source control.