03-02-2018 02:30 PM
@David_L wrote:
Thanks all, good tips. I think I like Kyle's idea the best if I can automate it. Editing lvproj as text files sounds dangerous. Maybe I can create a tool that does this then sell it and make a million
dollarskudos!
Use read txt file and do a search and replace in LabVIEW
Really, all the project file is is an xml file that project explorer uses to populate the views. Now you could use LabVIEW's Project Explorer to create save and edit this xml file OR, you can just replace text.
Its only dangerous if you write a bug
03-02-2018 05:42 PM
You could do this with scripting but I would guess that, unless this is a problem you run into somewhat often, it would probably be faster to just to do it manually. I love scripting but I usually spend more time making the tool than I save by using it.
03-05-2018 11:06 AM
@Jacobson-ni wrote:
You could do this with scripting but I would guess that, unless this is a problem you run into somewhat often, it would probably be faster to just to do it manually. I love scripting but I usually spend more time making the tool than I save by using it.
But that completely neglects the sense of pride you feel when you get the scripting functions to do what you want 🙂
03-15-2018 03:23 PM
So just to follow up, there was an alternative solution that I thought of which kind of helped. Since our project consists of one main project and multiple smaller dependency projects, I was able to temporarily add all code from all projects into the main project. Then when I made the library name change, it changed it everywhere. I just needed to do some clean up of the actual .lvproj files later, but mostly this worked out pretty well.
Overall, this change did cause some other weird bug which is still unresolved, but that's another story...