Application builder

[Saturn233207]

Greetings:  I've recently updated LabVIEW 2013 Full and performed reasonable driver updates in preparation to create applications and installer builds using the Application Builder.  Installers with LabVIEW run time engines, NI MAX, NIDAQmx, Visa etc. must be created for distribution to a number of production PCs.  Now, the NI Update Service saves installers to C:\ProgramData\National Instruments\Update Service\Installers.  This normally hidden system folder is > 18 GB.  If I delete these used installers to save space will the Application Builder still be able to create applications for installers that include all the updates up to today?  Rather an advanced question so I'd like to hear from NI or someone who has tried this before.

[billko]

I believe that the worst effect will be that your installer will no longer be able to find the install packages to include with your installs, so you'll have to have the original media.  (Which is unlikely if you used NI Update to get those packages.)  Maybe you can move them someplace more convenient so you still have the packages, at least, even if you have to go looking for them.

[Saturn233207]

Thank you billco for the response.  Was worried about this.  Just moving the update installer directories to USB HD or something will probably not work well as that will not redirect the Application Builder to the new location.  Not much time to experiment here.  Looking for a response from NI.  They are supposed to know how their programs work.  Have 'original  media' though but it is seriously outdated after 4 years.  NI must keep in step with MS Silverlight, .NET and c updates as these 'underpin' G code...  Was a time when (Symantec) Norton 360 decided that all NI stuff was a virus.  That was pretty awful but Symantec fixed it after some 'blog correction'... These forums are useful, even for a guy with 30+ years of NI experience.

Hello Mr. R. Hamburger if you are watching.

Lloyd

[billko]

I THINK that once you specify the new place for an installer, LabVIEW will remember the path for that installer.

[Saturn233207]

Thank you billco.  Not sure if I want to try deletion of those 'NI Installer' sub directories yet because 50% HD space still remains on the code development PC.  A pain to image it though with all the data and NI stuff.  Yes, need to train production staff how to zip and archive old data off the HD.  Takes a lot of tedious procedure writing to do that...  Seeking to learn from NI Support Staff exactly how their programs work and what is feasible in this particular case.  Can delete or move then restore later but business critical issues are present here.  Must avoid any big changes on the primary code development PC.  Will try on my laptop license though and see what happens with 'scrap code', no DAQmx, VISA or serial there though.  It is the more complex installers I am concerned about.

[DuncanW.]

Hi Saturn233207,

You can find a similar thread here. I know the solution is a tad vague in regards to building new installers, but this is an easy problem to test. Try moving the outdated installers to a separate folder and building a new installer using only the most recent patches. If your installer works on another machine, then you can delete all the old installers.

I suspect these patches build off one another, in that you cannot install more recent patches independently, but since this is a rather niche question, there is not very much existing documentation. Give it a try and let us know how it goes!

Best,

Duncan W.