hooovahh Posted October 10, 2018 Report Share Posted October 10, 2018 If there is a dependency added to a Pre/Post Install/Uninstall VI, this dependency isn't detected by the Scan for Dependencies function. Attached is a package that has a single VI that doesn't do much. But the package has a Pre-Uninstall VI that has a dependency on an OpenG Wait. Scanning for dependencies doesn't find any and I suspect it is because the Pre-Uninstall VI isn't part of the package source. The reason I want this is because my Pre/Post Install/Uninstall VIs are getting large and I wanted to make subVIs but they aren't brought into the package, only the top level. My work around for this is to call subVIs that are already installed. I intended on making a single package that is something like "Package Tools" which all packages that use the Pre/Post VIs will depend on. I can still add this manually but will often forget since all other dependencies are properly found on a scan. Reuse Test.zip Link to comment Share on other sites More sharing options...
Jim Kring Posted October 18, 2018 Report Share Posted October 18, 2018 Hey Brian, This is a great idea. You're right that VIPM doesn't scan the Custom Action VIs for dependencies, currently. I can see how that could be a big help. We can't commit to a date on this, but I'll add it to our tracker, for the R&D team to consider. Thanks! Link to comment Share on other sites More sharing options...
hooovahh Posted October 24, 2018 Author Report Share Posted October 24, 2018 I guess alternatively the Pre/Post VIs could be placed somewhere under the package source, so they are scanned. However for me I use the same Pre/Post VI for multiple packages and it is stored in a folder that isn't shared by any package. Thanks Jim. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.