LeahEdwards Posted November 16, 2022 Report Share Posted November 16, 2022 I found an issue last week where VIPM would give an error and the build would fail if I created a VI Package Build Spec which had a Windows Shortcut .lnk file in one of the folders. I had left a link to a PuTTY terminal session there for debugging. Here is a screenshot of the error it gives. I am using LabVIEW 2018 32-bit and and VIPM 2022.0 build 2371. If I build it again excluding the .lnk file, it works. Please find attached a minimal reproducible example containing a link to a child folder. I don't really need the issue fixing (I didn't need to include that file) but I was wondering if you wanted to handle it during the 'validating files' stage so the error message could be more specific as it wasn't obvious that the .lnk file was the issue. Many thanks, Leah link in repo.zip Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.