LabVIEW
Is LabVIEW’s Installer Engine officially deprecated? Windows SAC making it unusable.
I hope this doesn't derail things TOO much, but my company's been trying to switch to Intune-based software handling over our network. I don't have any experience with that, but my IT guy is reporting it's... not going great. He's had a lot of mysterious issues with it.
Any of you had success with the NIPM-based solution? It looks like it's got some CLI tools that probably make things easier, but there's a difference between theory and practice 🙂
@rolfk wrote:
Haven't seen any InnoSetup based LabVIEW toolkits anywhere. I mean, aside from the fact that project plugins are a pitta to create and debug, it would be absolutely not impossible to create a InnoSetup based project target option. It may not do everything you ever would like, but for a majority of applications it would be enough.
I saw a project provider toolkit made to make Inno setup installers. It was by VIE/Konrad/Averna? It wasn't ready for public release when I saw it but I thought there was going to be an effort to release it, but maybe not since I haven't seen anything.
I do use Inno Setup for getting around NI installer limitations. There are times I will make an installer in Application Builder, then call it silently from an Inno Setup to have more control over things, like multiple installers, Pre/Post install calls, registering file extensions, and running Powershell scripts.
@Hooovahh wrote:
@rolfk wrote:
Haven't seen any InnoSetup based LabVIEW toolkits anywhere. I mean, aside from the fact that project plugins are a pitta to create and debug, it would be absolutely not impossible to create a InnoSetup based project target option. It may not do everything you ever would like, but for a majority of applications it would be enough.
I saw a project provider toolkit made to make Inno setup installers. It was by VIE/Konrad/Averna? It wasn't ready for public release when I saw it but I thought there was going to be an effort to release it, but maybe not since I haven't seen anything.
I think the trouble with such a Toolkit would be that it relies heavily on semi- to non-documented LabVIEW details, NI's driver infrastructure and installer packaging. And of course an ever moving target as NI makes frequent changes to what drivers contain what elements and depend on what other software component and all that information is treated as "no need to know for anyone outside NI". That goes far beyond the change from MSI to nipkg and how they managed to make some nipkg installs even slower than the MSI installs, which already could be very bad. That alone would already be a major reason to try to use Innosetup which usually generates installers that are so instantaneous that you can't even show your nice logo in a meaningful way before the installer declares victory. 😀
