How to cleanly remove subvis from owning class

[PattyD]

I would like to delete a couple VIs from an owning class.  They are dynamically dispatched VIs.  I've found that some VIs have a "Remove from Project" right-click option while others don't.  They also don't have a File>Disconnect from Library option.  What's the best way to remove them?  Deleting them from disk causes LabVIEW to have a cow...

Worth mentioning the class is in an Auto-populating folder.

Thanks, PattyD

[dkfire]

In the project explorer, can you drag the vi out of the class and then save the vi and the class and then you could be able to delete the vi. 

[crossrulz]

I typically just delete the VI from the class/library, save the VI when prompted, then delete it from the disk.

[PattyD]

@crossrulz That first step is what I'm unable to do.  How do you delete it from the class/library?  Hitting delete does not work.  

@dkfire, It does not allow me to drag it out of the class unless i drag it into another class.  I'm a little stumped here.

[Kyle97330]

".lvclass" files are actually just text files with XML in them.  If all else fails, open them with a text editor, and delete it from the XML directly.

[crossrulz]

---

@PattyD wrote:

@crossrulz That first step is what I'm unable to do.  How do you delete it from the class/library?  Hitting delete does not work. 

---

That must be an artifact of the Auto-populating folder because I have been using the delete key to remove items from classes quite a bit lately (LabVIEW 2016).

[PattyD]

I suspect you are right crossrulz, but stopping the folder from auto-populating, saving, and reopening the project does not allow me to delete the files.  I would think that if auto-populating were the culprit this would fix it.

I will probably have to edit the lvclass file manually as Kyle97330 suggested.  I was hoping for something a little cleaner and included in LabVIEW though.

Thanks, 

PattyD

[PattyD · Accepted solution]

After a quick chat with NI we figured this one out.  I actually had another VI with the same name in my project (whoops).  Because of this, it wasn't allowing me to remove it from the class because then I would have two VIs with the same name in the project.  The solution was to rename them and then delete.