Uninstalling LabVIEW after an application (EXE) build

[Jick]

Hello,

I couldn't find any instructions for this. I have a LV project and build specification application.exe ready made. Now I want to uninstall labview and delete all VIs but keep all necessary components which are needed to run the application.exe. How do I know which are needed and which not when I start the uninstalling procedure? I use at least DAQmx and Vision Builder AI components. I can see items under Dependencies that VIs under a target require but it doesn't tell me what I need to uninstall.

Best Regards,

Jick

[wond3rboy]

You will need to keep the LabVIEW Runtime Engine and any neccesary modules(drivers) for your application intact. A better thing to do would be to make an installer for that application consisting of all the required stuff  Runtime Engine, any module and than uninstall LabVIEW. You can than install your installer. That would enable it be portable to other systems as well. This will help you to make an installer

http://digital.ni.com/public.nsf/allkb/9564F80C4DEBC4508625656900661050

[Jick]

There is no need to install my software anywhere else. It will be used on same computer. I would rather find out what modules to uninstall than play with the installer. Any other ideas?

Jick

[EvenDeejay]

I don't want to sound rude, but it takes you under 1 min to create an installer. Removing LabVIEW will take minutes, if not an hour, since the uninstaller remove module after module after module.... and so on.

In your project window, right-click on Build Specifications and select Installer.

In the Installer window, fill in desired information and where you want your build to be created.

Then add your source files (your .exe file) and where you want it to be installed.

Then add the run-time engine under Additional Installers.

Then remove your whole Labview if you want. And as mentioned in a previous post, run your installer after. You then install your .exe file together with the run-time engine. Note that if you use DAQ you should add the driver too, together with the run-time engine.

[wond3rboy]

Hi, you can post your VI, hope fully we can tell which modules you require.. But you can tell it by the functions that you have used.

[Jick]

OK, I try to play with the installer. I noticed that I have same problem ahead than I had before: I need to know which modules to include to the installer. But however this is safer method than uninstalling modules.

wond3rboy, this is quite big project (>100 subVIs) so I unfortunately can't send VIs.

Let's see what happens with the installer...

Thanks,

Jick

[falkpl]

we keep a virtual machine (actually several) for testing installers.  Install and test on the virtual machine, then rollback after testing.  This works if you plan on multiple deployments.  As for the installer, I would start with labview, Max and daqmx if you are doing daq, Visa if you are using serial, then look at the each toolkit to see if you need the runtime (ie vision, dsc...).  It would be nice if the installer looked at the project and dependancies and determined this automatically, maybe in LabVIEW2012 if we are lucky.

You might beable to test this on a second computer.

[Jick]

Yep, I am testing my installer on a second computer. But it's bloody slow to install/uninstall try other modules and install/uninstall...It would be a great idea to have automatic detection of modules! New idea?

Anyway, I have a question. Do I need to include NI-488.2 2.7.3 module if I use only basic GPIB Write.vi and GPIB Read.vis in my project?

BR,

Jick

[FraggerFox]

---

Do I need to include NI-488.2 2.7.3 module if I use only basic GPIB Write.vi and GPIB Read.vis in my project?

---

Yes, if you are making an installer