That's a good catch! Hopefully NI will see this and fill in a corrective action request (feel free to contact their support too) so you can at least select something else than a VI in the filters in the file dialog.
An easy workaround (and good practice) is to distribute your custom tool code as 2 pieces:
- The "main" launchable VI
- The support LLB that contains all the needed dependencies for the main to work.
You can apply this to custom workspace objects too.
Eric M. - Senior Software Engineer Certified LabVIEW Architect - Certified LabVIEW Embedded Systems Developer - Certified LabWindows™/CVI Developer Neosoft Technologies inc.