Can I use P4VS and P4SCC together?

Question

The project I'm working on uses the .NET Solution file and several C # projects. The IDE is Visual Studio 2012, and Perforce is used for version control. The .sln and .csproj contain SCC binding information, for example for .csproj files:

 <SccProjectName>Perforce Project</SccProjectName> <SccLocalPath>..</SccLocalPath> <SccAuxPath> </SccAuxPath> <SccProvider>MSSCCI:Perforce SCM</SccProvider> 

... and the .sln file:

 Global GlobalSection(SourceCodeControl) = preSolution SccNumberOfProjects = 43 SccLocalPath0 = . SccProjectUniqueName1 = AnotherProj\\AnotherProj.csproj SccLocalPath1 = . SccProjectFilePathRelativizedFromConnection1 = AnotherProj\\ SccProjectUniqueName2 = MyProj\u0020Domain\\MyProj\u0020Domain.csproj SccLocalPath2 = . SccProjectFilePathRelativizedFromConnection2 = MyProj\u0020Domain\\ ... etc ... 

According to Perforce , there is a transition process from P4SCC to P4VS:

Migrating from P4SCC to P4VS To transfer your solutions and projects from P4SCC, Plug-in Perforce SCC, to P4VS, you must do the following: 1. Separate the bindings from the solution file (.sln) and all project files (csproj, vcxproj, etc.) d.). 2. Remove MSSCCPROJ.SCC and other source-dependent files. 3. Move all developers to P4VS and remove the old P4SCC module. For detailed instructions, see www.perforce.com/perforce/doc.current/user/p4vs_p4scc_migration.txt .

However, due to the testing status of the project, these files cannot be modified. In addition, some developers prefer to use P4SCC.

Although I understand that the official process is that projects and solutions should be transferred (from P4SCC) to using P4VS, I remember reading an online comment (for which I have no link), where someone claimed that he is able to use both together without changing the project files.

Is it possible to do this without changing the Source Control provider every time I start, and click on a series of warning / error messages about inappropriate bindings? If so, how?

Answer 1

Sorry, this is not possible. You can install and use P4VS and P4SCC with different projects, but individual projects must be linked to the same source control provider.

Answer 2

It seems that VS2015 no longer modifies project files or solutions, unless you explicitly agree to remove the source bindings, even if you add a new binding. This means that now I can work with P4VS, while the rest of our team uses P4SCC, the only inconvenience is to re-select the source control and open the connection when opening the project. For me, this is a significant improvement, since it eliminates the risk that I accidentally send a solution or project with the removal of bindings.