LabVIEW
visarc generates dirty project using SVN source control
Hi,
I've read in different topics some issues related to the visarc file, but unfortunately, none of them helped me out. I was wondering if any of you came across this issue and found a solution or workaround to it.
The problem relates to a LabVIEW project which opens dirty, as you commonly say, under some circunstances. Below I will explain some of the problems I encountered as I tried to track this problem down.
1. I'm running a large LabVIEW Run-Time project using a PXI with several FPGA - cRIO.
2. I found that when opening the project file, this is perfectly clean and no asterisk shows in the title bar. I close the project and no saving is needed.
3. I open the project again and I open a sub-VI which contains the following code:
4. Straight away, the file visarc shows up under the Dependencies tree of the Real-Time PXI and the asterisk shows now on the title bar of the project (not the VI).
5. The VI closes without needed to be saved but the project says that an item was added, removed and added, and it has to be saved (as soon as I close the subVI above, the visarc file dissapears from the Dependencies section).
6. What I do next is to add this file visarc (located in Program Files\National Instruments\LabVIEW 2012\resource) to the project under the PXI tree. I then save the project and close it.
7. I open the project again, and it keeps being clean (not dirty, as you say).
8. I open the same sub-vi than before and everything keeps being clean and no saving is needed neither on the sub-VI nor the project. Everything goes smooth in my local computer from now on.
However, the issue that I can not resolve follows:
9. We are two people working on this project, and we're using SVN as source version control. Everything works fine in my computer, but when my partner update the files on his computer, the project opens dirty as soon as it opens (only the project, the sub-VI is no needed to be saved).
10. My partner just save the project and close it, and it becomes clean straight away in his computer. The files which are saved are the aliases file (I expected that), the labview project file, and the LVLPS File of the project.
This issue will happen again as soon as any of us downloads the SW committed by the other.
I hope any of you can help me out with this issue. Any suggestion or idea are welcome.
Thank you very much in advanced.
Best regards,
danidpr
