LabView and Perforce renaming a vi in your project

[KurtFriday]

Hi All

Im using Perforce as our SCC and I've integrated it into LabVIEW, all OK but I have a concern that hopefully someone can shed some light on.

If you use Perforce you will be awars that if you check out a directory then from File Explorer delete or rename  a file then Perforce is not forgiving and will not continue untill you give it back the file that you checked out. Fair enough and to do such opperations you should work within the Perforce Client.

However I would have expected that when you tell labVIEW that perforce id your SCC and within the Project manager you rename a file for the obvious reason that you want vi and control linkages to remap, that LabVIEW would execute the correct series of commands to perforce to tell it that the file has been renamed. Because when you go to check in your project folder Perforce wants that original file.

Has anyone experienced this and knows a workarround?

Cheers

Kurt

[billko]

---

@Kurt_Cochlear wrote:

Hi All

Im using Perforce as our SCC and I've integrated it into LabVIEW, all OK but I have a concern that hopefully someone can shed some light on.

If you use Perforce you will be awars that if you check out a directory then from File Explorer delete or rename  a file then Perforce is not forgiving and will not continue untill you give it back the file that you checked out. Fair enough and to do such opperations you should work within the Perforce Client.

However I would have expected that when you tell labVIEW that perforce id your SCC and within the Project manager you rename a file for the obvious reason that you want vi and control linkages to remap, that LabVIEW would execute the correct series of commands to perforce to tell it that the file has been renamed. Because when you go to check in your project folder Perforce wants that original file.

Has anyone experienced this and knows a workarround?

Cheers

Kurt

---

I use SVN and you can re-link the files.  With the Tortoise front end it's as easy as selecting both files and saying that it was renamed.  That way you keep the history intact.  Maybe you can do something to that effect?

[KurtFriday]

Hi Bill

I'll take a look and see if there is a similar capability.

I'm a great fan of SVN and have used it for years to SCC my LabVIEW projects, Perforce is new to me I'm getting familiar but I find the susff that was easy and intuative in SVN is not in Perforce

[billko]

I wished I could have been of more help.  😞

[nathand]

Unfortunately I've never seen any way to handle renaming/moving a file cleanly with Perforce and LabVIEW. I've always done it in two steps: rename the file within LabVIEW, exit LabVIEW saving all changes, rename the file back to the original, then execute the move/rename within Perforce. Cumbersome, but it does keep the file links correct within LabVIEW and maintains the history properly in Perforce.

[Hooovahh]

The two step method in my mind is always the safe way.  But if you are on SVN then you should know the ViewPoint SVN toolkit, and the older JKI one (which isn't free) performs renames in both places at once.

[KurtFriday]

Thanks Everyone

Ok its just confirmed my suspicions that this is the way Perforce and LabVIEW work. I think I'll just need to be carefull when I'm going to get LabVIEW to rename something for me, and work out an effective strategy.

Cheers

Kurt

[billko]

You can't do a rename in Perforce and continue from there?  That's what I do with VSS.  (There's probably a better way to do it in VSS, but I'm lazy and it works well enough for me.)

😞

[KurtFriday]

Hi Billko

The problem is when you work within a LV project you want to rename a vi, class or library within the LV project so that linkages are remapped. If you just renamed it in the Perforce client and then tried to open your project it will be looking for missing resources.

[billko]

Sorry, what I meant was after you rename it in your project, rename the Perforce file to the same thing and then commit.