OK, this is one I decided I should figure out eventually, and eventually is now here!
I have a number of LVOOP classes in my current project that I want to reuse in other projects. Accordingly, I want to move these classes to the user library. How do I do this effectively (without breaking the calls to the member VIs from other project files and without saving one VI at a time)? I have done this a couple times with small classes, saving each VI in succession, but I think there must be an easier way I'm missing....
moving LVOOP class to user library efficiently
Started by
PaulL
, Dec 18 2007 09:00 PM
2 replies to this topic
#1
PaulL
-
- Premium Member
-
- 462 posts
Extremely Active
- Location:Flagstaff AZ
- Version:LabVIEW 2011
- Since:1997
Posted 18 December 2007 - 09:00 PM
#2
Aristos Queue
-
- Premium Member
-
- 2,620 posts
LV R&D: I write C++/# so you don't have to.
- Location:Austin, TX
- Version:LabVIEW 2011
- Since:2000
Posted 18 December 2007 - 09:42 PM
Use AppBuilder to build a source distribution.
#3
PaulL
-
- Premium Member
-
- 462 posts
Extremely Active
- Location:Flagstaff AZ
- Version:LabVIEW 2011
- Since:1997
Posted 09 January 2008 - 11:05 PM
For the record, the following seems to work (thanks to NI support!):
Select the class in the Items tab in the project and do a Save As... Rename to put the class in the desired folder in the user.lib.
Then in the Files tab select the class methods in the old location and use the Move on Disk... option. The old directory will disappear from the Files view if there are no other project files in that folder. (Be mindful that any files that may have been associated with the class but are not part of the project could still exist on disk.)
This method requires a bit of care but seems to work OK and is reasonably efficient. I did encounter some issues with my project, but I think they are related to other issues with the particular project file.
Select the class in the Items tab in the project and do a Save As... Rename to put the class in the desired folder in the user.lib.
Then in the Files tab select the class methods in the old location and use the Move on Disk... option. The old directory will disappear from the Files view if there are no other project files in that folder. (Be mindful that any files that may have been associated with the class but are not part of the project could still exist on disk.)
This method requires a bit of care but seems to work OK and is reasonably efficient. I did encounter some issues with my project, but I think they are related to other issues with the particular project file.
