From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
12-28-2021 04:07 PM
My project has been used in several clients test equipment. More or less every client needs some special VI:s that are not used in next clients testeq - but still are stored in the folder. Furthermore, the development process making some vi-files no longer needed and should be deleted. Some Vi:s are only test prototypes. This means that the folder growing in a way I don't like. Some times I can see VI:s that are used but aren't in the project (lvproj). How come? Some times they are created in lvproj and sometimes not.
Question; Is there a way to cleanup the folder and project (.lvproj) from files (vi, ctl...) that are not part of the EXE-file? Some file-list that I can compare whats really in the folder?
I thought of mass-compile but that process does not alter the files date/time.
Solved! Go to Solution.
12-28-2021 08:43 PM
Ouch! Am I correct that your code is not under some form of Version Control? The Good News is that you realize that you have a serious problem ...
Bob Schor
12-28-2021 11:57 PM - edited 12-29-2021 12:44 AM
I use git to keep track of the project. I can clone the project but if I do that, I get all the files in the folder, used and non-used files. Perhaps I can in some way use git to sort out which files are in use or not.
edit: I right clicked the project name in the Project Explorer. There was a choice "Find Items with no Callers". I could export the file list and import it into Excel where I could sort the list and get important information. Perhaps that is a way forward.
12-29-2021 08:11 AM
You might want to take this opportunity to do some refactoring of your project. Break up the code into libraries. You may even go so far as to create a new project in order to build the common libraries into Packed Project Libraries. Each of your client projects should be in their own project and repository. I actually copy the PPLs required for the application into the project folder/repository so I can lock down which version of the PPLs I used.
12-29-2021 10:11 AM
@TakeANap wrote:
This means that the folder growing in a way I don't like. Some times I can see VI:s that are used but aren't in the project (lvproj). How come? Some times they are created in lvproj and sometimes not.
The 'extra' VIs should be in project dependencies, that you can show by right clicking the root, and then View>Dependencies.
On each dependencies you can right click and select Why is this in dependencies or find callers.
12-29-2021 03:05 PM
Ok. I understand how you thinking and how I should handle a project. I have never need to deal with this kind of projects before. Just small applications that contains 1-20 files.
I need to identify the main parts of the application and make a template of it - I think.
12-29-2021 03:09 PM
I will look into PPA:s. It is time for that now. I can not continue as I do now.
I have read the headline about PPA but have thought it was too much for me at the time to read and use.
12-30-2021 06:12 AM
@TakeANap wrote:
I will look into PPA:s. It is time for that now. I can not continue as I do now.
I have read the headline about PPA but have thought it was too much for me at the time to read and use.
PPAs? If your search doesn't give the right hits, search for PPL instead.
12-30-2021 07:12 AM
Of course PPL. I had Linux-stuff in my head. 🙂