LLB

[nyc_(is_out_of_here)]

LabVIEW 6.1

I have an LLB that appears to have some LabVIEW built-in VIs included in it.

I want to remove those VIs that are a part of LabVIEW and just include only VIs that were written for this program.

I hope that makes sense.

Can this be done?

If so, how?

I have used the VI Library Manager tool to unpack the VIs from the LLB to a directory.

I am not sure which VIs are safe to delete.

[Dennis_Knutson]

Back when I was first using LabVIEW, I made the mistake of selecting 'include VIs from vi.lib' when I created an llb. This resulted in errors when upgrading to a new version.

You do have the option of directly deleting specific VIs from an llb without converting to a folder. I don't know of an easy way to determine which VIs came with LabVIEW and which were custom. Mostly depended on recognizing the names. Could you provide a list of the llb contents? Maybe someone else has a better idea.

[Norbert_B]

VI Names is one thing...but there have been situations in the past where developers copied LV included VIs into custom LLB in order to change the code of the LV supplied versions.

It's nothing wrong with altering NI provided VIs and putting them into a custom LLB as long as you also change the name.

Coming back to your issue:

Even if you list all VIs in the LLB and compare the VI names to VI names in vi.lib, you still don't know if the VI in the VI was altered. Or if the current LV includes changes to that specific VI(s).....

Essentially, you are currently on the task to find "crosslinking" and to remove conflicts. The best option to perform this is discipline:

- Always check the VI hierarchy (or files tab from a lvproj!) for correct paths!

- Check the lvproj for conflicts. Create dummy VIs to load VIs from the vi.lib before loading the LLB in order to create conflicts if the LLB contains equally labeled VIs.

Norbert

[sth]

I would first extract all the VIs into a folder.  (not necessary but it makes life easier).

Then write a VI that iterates over the list of VIs in the folder and check each one for the "Is System VI" property.  This *should* have been preserved while when saved.

[nyc_(is_out_of_here)]

---

@sth wrote:

I would first extract all the VIs into a folder.  (not necessary but it makes life easier).

Then write a VI that iterates over the list of VIs in the folder and check each one for the "Is System VI" property.  This *should* have been preserved while when saved.

---

Is this property that can be seen if I open up a VI manually?

[sth]

---

@nyc_(is_out_of_here) wrote:

Is this property that can be seen if I open up a VI manually?

---

No.  That is why I suggested it the way I did.

[nyc_(is_out_of_here)]

---

@sth wrote:

---

@nyc_(is_out_of_here) wrote:

Is this property that can be seen if I open up a VI manually?

---

No.  That is why I suggested it the way I did.

---

Okay. Thank you.

[mikeporter]

Another good way of determining built-in VIs is to look at the icons. If they are NI's VIs they will typically have pretty nice looking icons. Most developers don't take/have the time.

Mike...

[nyc_(is_out_of_here)]

---

@mikeporter wrote:

Another good way of determining built-in VIs is to look at the icons. If they are NI's VIs they will typically have pretty nice looking icons. Most developers don't take/have the time.

Mike...

---

Looks like I found most of them.

For some reason though I am having trouble with the Windows Registry Access VIs.

If I delete them, LabVIEW wants to compile them and complains about now being able to save them.

I have decided to leave those alone.

I am a contractor here, and they do not seem to want me to spend too much time with the details. Ah, well.

[mikeporter]

LV want to compile them when you delete them from Windows Explorer? What do you mean?

Mike...