Jump to content


Branched projects not bound to source control


  • Please log in to reply
1 reply to this topic

#1 p4bill

p4bill

    Advanced Member

  • Members
  • PipPipPip
  • 175 posts

Posted 10 April 2019 - 02:29 PM

moved from this post:
https://forums.perfo...__20#entry24653

We're using Perforce and Visual Studio. Whenever we create a branch, some projects will not be bound to source control unless we use "Open from Source Control", but other projects work regardless. From my investigations, I know some of the things involved:
In our .csproj files, there are these settings:
  • <SccProjectName>
  • <SccLocalPath>
  • <SccAuxPath>
  • <SccProvider>
Sometimes they are all set to "SAK", sometimes not. It seems things are more likely to work if these say "SAK".
In our .sln file, there are settings for many of the projects:
  • SccLocalPath#
  • SccProjectFilePathRelativizedFromConnection#
  • SccProjectUniqueName#


#2 p4bill

p4bill

    Advanced Member

  • Members
  • PipPipPip
  • 175 posts

Posted 10 April 2019 - 02:41 PM

If I am understanding your description correctly, this is expected behavior. P4VS will not mark solutions as under source control unless they are opened from the depot (via "Open from Source Control") or added to source control with P4VS from within Visual Studio at least once.

If you have a branched (and synced) project on you local machine but it has not been registered as controlled, you should see a message when connected to a server and opening that solution:

"The solution file needs to be registered with P4VS. Would you like to check out the solution file to complete the registration?"




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users