Ability to Unregister an Add-on?

[vishots.com]

Why is there no consideration for unregistering an Add-on? How can this be done?

[sohum]

Add-ons are automatically unregistered on the next launch of LabVIEW after uninstallation, where unregistered is defined as being removed from the start-up dialog box.

[vishots.com]

And by "Uninstallation" you mean removing the licence file? I tried deleting the license file and the Addon library. However the (now Invalid) toolkit still shows in the Add-ons list. Even after restarting LabVIEW. I assume this info comes from the registry? How and when is the registry cleared of this information?

[Jervin Justin]

From my understanding:

1. On LabVIEW startup, LabVIEW will check the registry for add-ons
2. For each "registered" add-on, it will check for the add-on library (.lvlib)
3. If it can't find the .lvlib, it will assume that the add-on has been uninstalled and will take it off the list of "registered" add-ons.

I just tested this with one of my libraries. Removing the .lvlib file that is pointed to in the registry "unregisters" it.

For the correct path of the .lvlib, look at the HKLM » Software » [Wow6432Node if 32 bit LV in 64bit] » National Instruments » LabVIEW » 10.0 » Partner Addons

[vishots.com]

Thanks Jervin.

By looking at the registry, I can see the problem. The path is pointing to the library in my source. I tried to run a VI in my library after I licensed it and LabVIEW must have used that as a trigger to "Register" it. It used that path and put it in the registry.

If I had run RegisterAddon (which I didn't). Would the registry get updated with the path to the installed library?