LeahEdwards

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

No problem, thank you!

So this feature is not coming to Free? It seems to work in Community already. In that case, I'll add that to the list of reasons to buy Pro.

Scratch that, I've found it in the API! Missed it first time I looked. Edit: But I see now that it works for Community but not Free. Will this change for VIPM 2023+?

Thanks for clarifying @Jim Kring. The new documentation centre looks great, handy being able to edit too. Unfortunately I don't think I will be able to use VIPT files for what I need to do. I have a template LabVIEW project which has a VIPC, and I want to replace every instance of the word "TEMPLATE" in the VIPC when a new project is spun up. This includes places like the product description summary, product description and pallette names. I believe in the past I would have been able to edit the xml of the VIPC but it seems that it doesn't work on VIPM Free any more, and I can't guarantee the template users will have Pro. Am I missing something here?

I stumbled upon these today in VI package builder under File > Save As Template , but I am struggling to find the documentation. Am I right in saying they allow you to set the Source Directory, Product Name and Company Name upon opening the .vipt file (including where they are used e.g. in automatic package filename), but pre-set other fields of the new .vipc?

Hi Jim, Thank you for looking into this and explaining what is happening. Looking forward to seeing which solution you go with. Kind regards, Leah

Hello, I was delighted to have a VIPM community package published recently. However, I have noticed a discrepancy between the package description on the Community Package Page vs in the VIPM browser: I had a few placeholders in '<>' tags in the package description text but they do not display on the Community Package Page. I don't see them in the page source either - they have been stripped away. Here's what I mean: Community Package Page: https://www.vipm.io/package/leah_edwards_lib_tortoisegit_show_log___quickdrop_plugin/ In VIPM Browser - Tags displaying as I intended On page: <nothing> and <shift modifier> are missing. I can't remember now whether I typed the description into a box during submission or whether it was auto-copied from the package. Either way, I don't remember seeing a warning about tags, but I might have missed it. Perhaps it's being stripped away because it looks like html formatting. Is this something you were aware of? I am happy to resubmit my package after swapping '<>' for something else e.g. '[ ]' . Or if there are actions that you could take to prevent this on your end, let me know! Many thanks Leah