ni.com is currently undergoing scheduled maintenance.

Some services may be unavailable at this time. Please contact us for help or try again later.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Help with project cleanup


@bemoore wrote:

 

Using dependencies... does this also imply that every vi that shows up in dependencies should be added to a project virtual folder?


Don't add any dependencies that are part of LabVIEW (e.g. vi lib). Personally, I prefer to add all dependencies that I wrote myself, but it is not absolutely necessary.

 

You are really dealing with two different problems: (1) cleaning up the project, (2) cleaning up the local folders.

0 Kudos
Message 11 of 15
(265 Views)

I discovered this going through items one-by-one. I'd find, say, a control with enum entries that apply to a different project. But it has a caller. And that caller has a caller. But the 3rd level up... no more callers. That REALLY makes the one-by-one cleanup process painfully slow.

0 Kudos
Message 12 of 15
(264 Views)

I found 3 vi's in dependencies that were from a LabVIEW example. I added them to the project. I copied them to a local folder. Then I did a "Replace with..." in the project, replacing the links to the example vi's with links to local vi's.

 

I'm trying to clean up the project and folders. A few of the project folders were snapshot populated. I was able to remove entire virtual and physical folders in a few cases. A few of them bit me, though, when the top level vi failed to open. So then I'd have to undo some of my steps. I came here to find a better way.

0 Kudos
Message 13 of 15
(262 Views)

@bemoore wrote:

Source control... I'm the only LabVIEW programmer in the building. There are probably a few more in the company somewhere, but they have nothing to do with this project. I'm not I could convince anyone to implement source control for this.


It doesn't matter if you have to share the code. I am also a lone developer, but everything is in Git. This has saved me many many times as it allows descriptive snapshots of where things were, what changed, etc. And if I mess something up, I can just do a revert and I am back to a known state. That is the point of SCC. I would recommend just using whatever SCC your other software developers are using, which is how I was forced to start using Git instead of SVN (no regrets in that regard).



There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 14 of 15
(244 Views)

I've used Git and SVN, and I can say that the best option is the one you actually use 🙂 I wouldn't overthink deciding between the two. If all else is equal, I'd recommend Git, but honestly it took a LONG time of using SCC at all before I had a preference as to which one to use, especially if you're a solo dev.

0 Kudos
Message 15 of 15
(204 Views)