Does Application Builder support Zip File build specs?

[MichaelBalzer]

Hi all,

Simple question - does the Application Builder Build.vi support Zip File build specs?

Running Build.vi with a Zip File build spec input doesn't produce any output on disk, but doesn't produce any errors either. All of the source files for the zip build spec exist, and the owning project is saved immediately before the call to Build.vi. It'll happily build Application and Installer build specs.

[ewang52 · Accepted solution]

This is actually a bug that National Instruments was recently made aware of. There was a Corrective Action Request that was filed and the number is 611405 if you would like to track this issue. Look for our bug fixes in future releases!

I would also suggest using source distribution and zipping externally if you need an immediate fix.

Eric Wang

Applications Engineering

[MichaelBalzer]

Thanks Eric. Good to know I'm not doing something silly on my end. My fall back plan was externally compressing the files, so it's not a deal breaker.

[Yamaeda]

---

@MichaelBalzer wrote:

Thanks Eric. Good to know I'm not doing something silly on my end. My fall back plan was externally compressing the files, so it's not a deal breaker.

---

You should be able to use the Post build VI to compress the Distribution. I haven't tried it myself though.

/Y

[M.Julien]

Hi,

We still have this bug in LV2015 SP1 f7.

Where we can find the status of the CAR 611405 ? And generaly for any CAR, searching each versions of LabVIEW and Service Pack is very tedious... and with no certainty to find out...

A good idea could be to have one place where we can find all known issues AND their status ? We are all developer and probably professionnal so we don't have time to waste: in searching accross entire web site without any warranty to find it ; or to spend time to develop a workaround whereas a fixes come in near future!

Thanks.

[anson.kunjappy]

M Julien,

I looked into the status of CAR 611405 and it has been closed. Notes on the CAR show that a fix has been implemented in LabVIEW 2017. Unfortunately LabVIEW 2015 will still have the bug because LabVIEW 2017 will be the earliest version with this fix.

Thanks