07-15-2020 11:41 AM
Greetings,
This has been an ongoing issue for me. Moving my project from one computer/lab to another "brakes" project structure requiring re-linking files/libraries and other operations making this process quite painful.
The most recent move (LV 2017 to LV 2020) seemed to break down altogether. Most libraries did not load at all. It seems there was a way to make it work, but it required deleting/renaming lvlib file, removing from project, and re-entering it ... for each library!
This is the setup:
The file hierarchy is pretty organized I think. The main project resides in the top-level folder. Each library (as seen in the project explorer) is contained in a sub-directory with its on lvlib file in the sub-folder.
Both systems have all LV components and drivers installed (we do control both computers).
I was hoping to copy the top-level folder with all sub-folders and migrate to the new computer. Wrong. Most libraries did not load ... I am not sure why.
I have been reading on-line and it appeared that in the file hierarchy is "clean". a simple copy/paste should suffice. This was not my experience.
I would appreciate any insights or suggestions how to resolve this particular issue as well as future transfers of the project between different machines.
Thank you.
Radovan
07-15-2020 11:50 AM - edited 07-15-2020 11:58 AM
Quick and dirty solution: on your project window, go to File -> Save As... and the resulting top-level folder will have all dependencies mapped correctly. You can then copy/paste that to another computer.
edit: forgot to mention to select the option to Duplicate .lvproj file and contents, and the option to Include all dependencies.
Saying "Thanks that fixed it" or "Thanks that answers my question" and not giving a Kudo or Marked Solution, is like telling your waiter they did a great job and not leaving a tip. Please, tip your waiters.
07-15-2020 12:10 PM
Try saving the project using "Save for a Previous version" before you move it.
This should pull all the dependencies and retain the paths and etc. so you shouldn't have to relink everything.
07-15-2020 12:10 PM
The only time I had any issues remotely like this is when I was working on a project and the lead engineer made me copy my libraries for different programs (on the same project, it was a big mistake). I fought cross-linking issues constantly because I had to go back and forth so much even though the directory structures were "clean".
Your image looks like you have conflicts in your project. Hit that "Resolve Conflicts" button and see what you have. These can cause libraries to not load.
My other piece of advice is to use some type of Source Code Control (SCC). First of all, it is by far the best way to distribute code among you team. Secondly, it keeps a history of what you have done and lets you revert as needed.
07-15-2020 12:11 PM
Thank you for a lightning-fast response.
I did see this as a suggested solution, but my "Save As" is greyed out (for whatever reason) -- this is under File>Save As in the Project Explorer window.
Honestly, I do not see reason why "Save As" and copying those files would be any different from copying the "original" directly, but I will give it a go .. as soon as I can un-grey the "Save As" option ...
What I do not understand why RGA library worked. I have also spent about 20 minutes re-integrating DAQ library (seen near the bottom) ... and it works now. I just do not feel like doing that for more than dozen libraries :-).
Thank you.
Radovan
07-15-2020 12:13 PM
Thank you ... I will try that ... that option was not greyed out :-).
Working on it right now ... I will post the result ...
Thanks again!
Radovan
07-15-2020 12:27 PM
@crossrulz wrote:
Your image looks like you have conflicts in your project. Hit that "Resolve Conflicts" button and see what you have. These can cause libraries to not load.
It looks like the conflicts are due to location of RGA driver (from LV2014 ... the original location in LV 2017 and the current one under LV 2020). No other conflicts related to "Not Loaded" libraries.
@crossrulz wrote:
My other piece of advice is to use some type of Source Code Control (SCC). First of all, it is by far the best way to distribute code among you team. Secondly, it keeps a history of what you have done and lets you revert as needed.
I did see people mentioning some sort of version control ... I have recently started using git/github. There is a "Getting started" page ... reading it next :-).
Thank you.
-- R>
07-16-2020 10:14 AM
Hi,
A quick update.
It was the Bromium!!! The project has been transferred to a managed computer. There is Bromium software installed to monitor and isolate suspicious files. I suppose LV library file falls into that category. It prevented LV from accessing that file before user cleared it as safe. After ALL .lvlib files were cleared, LV project was able to lead them.
I suppose there was a hint in the LV error message when it failed to load the library ... "check firewall settings" ... well it is a brand new computer and I do not have admin privileges ... all the fun stuff!
Thank you all for help. I am setting my git repo locally and slowly migrating my LV code there and eventually share it via github ... hopefully that will alleviate al least some of the migrating and sharing issues.
Best,
Radovan