Uninstall option for LabVIEW build application

Hello All,
I want to create a Uninstaller for and LabVIEW application created in 8.5.
Please give your suggestion for how to create....
Regards,
Bharathi T

This is still valid in LabVIEW 8.5, if you build an installer it will show up in the Windows program list.
Ton
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas
LabVIEW, programming like it should be!

Similar Messages

Uninstall Option for a package is grayed out in Software Center 2012 Client side but others have it available

Hi,
I created a deployment for an application that will use a Custom CMD to Install / Uninstall. Locally executing those files works perfect. The deployment installed the application and shows perfectly installed but:
Since this application is a user Self Service Application they should be able to hit to Install or Uninstall by themselves. The problem is that the Uninstall button is grayed out.
I noticed this problem for other applications too but some of them has this option available.
My question is if only the MSI Native Installer will get this option available or also the Script Installer can have it available.
I do have a Uninstall Program listed on the Deployment type as: "uninstall.cmd" before it hasn't had the quotes but even that still doesn't active the option Uninstall. I don't know if there is an option inside the UDI Wizard that I missed
to activate that will activate this option for this kind of deployments.
Please any ideas on what I'm doing wrong?
Kind regards.

Hi All,
I have the same problem like Joel, But my deployment is available and does not have a query to detect installed users. we have used direct membership in collection, still the option of uninstall is graded out for one of the application.
So far we have tried all the below options.
Created a new application and deployed to the targeted audience – Still not worked
Changed the detection method to Product code – Still not worked
Change the uninstall script – Still not worked
Refreshed client policies – Still not worked
Reboot is not pending – Still not worked
Policy Reset – Still Not worked
Client Repair – Still not worked
WMI Repair – Still not worked
Let us know any other solution/though to resolve the issue.
Regards,
Sri

Uninstall options for an AIR application

Hey all,
when distributing an air app is it possible to have any control over
the install/uninstall process(.air)?
For instance i want to put an "uninstall" link on the start menu to
make it easier for the user to uninstall the app.
And also when the app is uninstalled i want it to remove a db file
that is created at run-time in the user folder.
Is any of those possible?
Thanks in advance

Hi,
I have the exact same question.
I aswell noticed that files in the applicationstoragedir are not removed when uninstalling your app.
Hope someone from adobe can help us with this one.

Compiler options for release build

I am using Ant to build a series of swfs in an Actionscript project and I want to compile them as small as possible, but I can't compile them as small using Ant and the mxml compiler as I can compiling in FB using the Release Build. What options can I use to emulate the FB release compilation?
I use optimize=”true” and debug=”false”
I have also seen this asked here:
On: http://flex.gunua.com/?p=79 Chris asked:
Does anybody know why the swf file is bigger when compiled by Ant, as opposed to when it’s done by the Flex Builder. It is even smaller (1/2 the size) when I use the “Export Release Build” option.
I am using optimize=”true” and debug=”false” in the mxml task, but it does not seem to be enough.

Hi Josh,
I think this should help. The -dump-config option should help you get what you want.
http://help.adobe.com/en_US/flashbuilder/using/WSbde04e3d3e6474c4-59108b2e1215eb9d5e4-8000 .html#WSbde04e3d3e6474c4-59108b2e1215eb9d5e4-7ff0
Nishad

Remote save for report builder

CF Report builder does not have an option to save .cfr file
to remote server (rds). I don't have CF installed on my client and
every time I make changes to .cfr file I have to upload to the
server.I wish they had remote save option for report builder like
CF studis or deamweaver.

My solution was to keep the cfr in the same place as the rest
of the application. Since when creating a cfr I usually have DW
open along with it, i just switch back to DW after a save and
upload the cfr from DW. Not really that big of deal, or I am just
used to now.

Building Shared Object for LabView

All;
I'm trying to build a C++-based shared object to be called from LabView and use SunCC instead of gcc. The compile stage looks like:danny@traveler:~/tubes/dielectric/rod_software/lookup> make -f Makefile.unix suncc=1
sunCC -I/usr/local/lv71/cintools -I/home/danny/src/NR_C301/code -c -KPIC -m32 -Di686 lookup.cc
"/home/danny/src/NR_C301/code/interp_1d.h", line 183: Warning: n hides Base_interp::n.
"/home/danny/src/NR_C301/code/mins_ndim.h", line 103: Warning: n hides Linemethod<extern "C" double(const NRvector<double>&)>::n.
"lookup.cc", line 176: Where: While instantiating "Powell<extern "C" double(const NRvector<double>&)>::minimize(const NRvector<double>&)".
"lookup.cc", line 176: Where: Instantiated from non-template code.
2 Warning(s) detected.and the load stage fails like this:sunCC -G -m32 -o lookup.so lookup.o /usr/local/lv71/AppLibs/liblvrt.so.7.1 /usr/lib/libGL.so /usr/lib/libOSMesa.so.6
/opt/sun/sunstudio12/prod/lib/crtn.o:(.text+0x0): multiple definition of `_etext'
make: *** [lookup.so] Error 1Is my problem obvious? Is there a simple example on how to build SOs? I found the switch definitions in the Sun documentation, but no good examples yet.
...Dan

If your library links to other shared libraries, use -L options to point to directories other than system directories, and the -l option for the library name after "lib".
When building shared libraries, you also need to list all system libraries explicity, unfortunately, to ensure your library has the right dependencies.
You should also add -zdefs to force the linker to complain about unresolved symbols. The default when building shared libraries is not to warn about them.
You want to be sure you have included all the needed libraries in the link.
Your link command should look like this :
sunCC -G -m32 -o lookup.so lookup.o -zdefs \
-L /usr/local/lv71/AppLibs -llvrt.so.7.1 -lGL.so -lOSMesa.so.6 -lCstd -lCrun -lm -lcYou don't need a -L option for /usr/lib or the directories in the Sun Studio installation. The CC driver knows where to find system libraries.
That said, I don't think the command line issues are the cause of the multiple definition error.
Binaries created by Sun C++ are not compatible with binaries created by other C++ compilers like g++. Is liblvrt.so.7.1 a g++ library?

MS Office Starter No option for Change or Repair only Uninstall.

Re installed OS. No problem but lost MS Office Starter. Message that Q is being used and it must be empty.Tried as advised to click MS Office in program panel but only option was for Uninstall. No option for change or repair. Now what?

Didn't what I posted to your other post the other day at the link below work? It did for me and many others... http://h30434.www3.hp.com/t5/Desktop-Operating-Systems-Software-Recovery/After-reninstalling-cannot-access-MS-Office-Startr-2010/m-p/5154049

Functions in IMAQ Vision for Labview same as those in Vision Builder?

Hi all...
i just have a simple question..Does IMAQ Vision for Labview has the same functions of Vision Builder?
I know that with Vision Builder you can develop an application interactively...but does it has more functions than IMAQ Vision?
So if i buy IMAQ Vision can i develop the same kind of applications that i would make with Vision Builder?
I´m specially interested in color matching and color analisys functions.
Thanks

IMAQ Vision has much more than Vision Builder. Basically, VB was created using Vision and they implemented a good number of the functions in a menu driven format. However, there are many more functions available that were not integrated into VB.
Vision does have some good color matching and analysis tools.
Bruce
Bruce Ammons
Ammons Engineering

Why are the NI-DAQmx Base for LabVIEW options grayed out using custom install (with Action:Skip)?

I'm trying to install NI-DAQmx Base 3.7.0 for LabVIEW 2013 (LV is installed). When I try Standard Install, it doesn't install for LabVIEW (only the Common and C and USB tools), but gives a successful installation message.
When I try Custom Install, all of the "...for LabVIEW 20XX" options are unchecked, grayed out and the Action says "Skip".
I'm trying this on a 2011 MacBook Air 11" running OS 10.9. LabVIEW runs fine.
Thanks for any suggestions.
Solved!
Go to Solution.

Hi,
OS 10.9 is not officially supported by NI with the DAQmx Base 3.7. This information is from the description of the driver (http://www.ni.com/download/ni-daqmx-base-3.7/4272/en/):
OS Support—NI-DAQmx Base now supports the following versions of Mac OS X:
Mac OS X 10.7 (Lion)
Mac OS X 10.8 (Mountain Lion)
So this seems to the be the problem. Either you choose another OS version or wait for a new driver which supports 10.9
Regards,
Michael

LabVIEW version for Vision Builder AI 2012 plugins

Hi all,
Ii was a bit of a challenge to find out which version of LabVIEW was necessary to develop custom plugins for Vision Builder AI 2012, I found it by starting the installler, it is LabVIEW 2011 (but I wish I could find this information in Vision Builder AI 2012 readme file).
Now my question is : is it possible to use LabVIEW 2011 SP1 to develop custom plugins for Vision Builder AI 2012?
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"
Solved!
Go to Solution.

Right... I tried, I installed all the VBAI and LabVIEW versions I could.
I turns out LV 2011 sp1 is just an upgrade of 2011 and as such LV2011 SP1 can be used to develop custom plugins for Vision Builder AI 2012.
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Building Dll for labVIEW RT gives errors

Hi All
Does building dll for labVIEW RT using CVI require labview runtime engine to be installed?
becuase i get some errors of unsatisfied referances to some library while building the dll with target selceted to "labVIEW real time only".
Regards
Arun

Hello Arun,
You don't need to have LabVIEW Run Time installed on your machine. Please check the link below to see the function that are supported by exporting the LabWindows/CVI LabVIEW RT Engine
http://digital.ni.com/public.nsf/websearch/D3EFE7C6F073384886256FDD005FBCDA?OpenDocument
Ame G.
National Instruments

Where is the doc for xml task options for deploy and ojdeploy-build ?

I am a new user.
I tried using jdev help to find my answer, but got lost quickly in the zillions of manuals.
1) Where is the manual/doc for the xml task attributes/options for the Ant tags <deploy> and <ojdeploy-build>?
I am modifying an xml script that ojdeploy will call, but do not know what attributes/options are supported for these tags. I need to know whether an option such as failonerror exists, so that I can report a bug that <deploy> does not default to fail on error (or that <ojdeploy-build> ignores the error and continues with the script.
Followup questions:
2) How do I find the java code that implements the tags <deploy> and <ojdeploy-build>?
3) How do I report a bug on the implementation for these tags and propose a fix (assuming I can see the java source code)?

I guess I wasn't clear enough. What I tried to say was:
1) Where is the manual/doc for the xml task attributes/options [I meant to say attributes/elements] for the Ant tags [I meant to say tasks] <deploy> and <ojdeploy-build>?
I did not mean the ojdeploy command, but the Ant tasks <ojdeploy-build> and <deploy>.
The jdev help does not seem to provide the complete list of elements or attributes for these critical Ant tasks, though it has a few examples.
So far, it appears that <deploy> has been misdesigned and I cannot do what I want, which is to "failonerror" (failonerror="true" should be the default but the opposite is true and there is no attribute to change the setting).
You could consider this to be a bad flaw in Ant itself, that you cannot get the exit code from every Ant task (since they are java programs they do have an exit code), so when new tasks are implemented by folks who lack experience they may leave out access to this programming feature that is however implemented for a bunch of important core Ant tasks such as "java" or "exec". It would have been far more useful to make this a generic feature of all Ant tasks. Of course then folks would be asking for stuff like "fail if" or "fail unless" and where would it end? Maybe with a real programming language like TCL but in XML form.

Creating Activation code for LabVIEW Application Installer

Hi,
How could we create Activation code for LabVIEW Application Exe to restrict use to Single PC using LabVIEW settings/add-ons.
I think NI should provide in-built feature in Application Builder to generate activation code as required.
Regards,

Or just vote for this idea.
Try to take over the world!

I find dirivers hp4142B for labVIEW applications

i would like to make an application with labVIEW and i need download a driver for hp4142B (it is a polarizzatore)

Hello "i find drivers hp4142B for labVIEW applications",
Unfortunately, I was unable to locate a driver for your hp4142B. I was able to find a driver for the hp4140 which may either work directly or work with minimal modification.
If you would like to try developing your own instrument driver (or modify the existing one), we have documentation, model instrument drivers, and driver templates to help at :
http://www.ni.com/devzone/idnet/development.htm
We also have a syndicate of third party vendors that specialize in National Instruments' products and services. Some of the vendors specialize in driver development. I would suggest contacting one of the Alliance members at:
http://www.ni.com/alliance
An instrument driver is a collection of funct
ions that implement the commands necessary to perform the instrument�s operations. In short, someone read the instrument user manual and implemented some of the functionality in a program for the end user. Instrument drivers are not necessary to use your instrument. They are merely time savers to help you develop your project so you do not need to study the manual before writing a program.
There are example VI's in LV on Instrument Connectivity. If you go to the Help menu >> Examples.. >> I/O, you will see a couple and Examples.. >> Fundamentals for File and String manipulation. I would suggest tweaking them to suit your application. Also the specific command that your instrument responds to can be found from it's manual.
Some useful resources for your application are
ni.com > NI Developer Zone > Development Library > Instrument Connectivity
http://search.ni.com/?col=alldocs&layout=TechResources&ql=a , to search examples and knowledge bases
Hope this helps!
Best Rega
rds,
Aaron K.
Application Engineer
National Instruments

Determine (and Minimize) LabVIEW Build Dependencies?

Is there a way for LabVIEW to analyze a project and determine auto-magically exactly what additional installers need to be included with the main program installer? It seems to know it needs to add the associated run-time engine but that's it. This wouldn't be so bad if adding something like DAQmx or IMAQ didn't take your distribution size from 1MB to 1GB (only slightly exaggerating there).
Which brings up another question: Can you just install drivers for the one or two hardware devices you're actually using in your program or is a full DAQ installation the only option?
I'm trying to get away from the evils of both extremes.
Too Much: Check off everything you think might be applicable and know that it will install but it will be a slow install of a ridiculously huge distribution file.
Too Little: Pare it down to the bare bones and get those disgruntled emails when IT can't install your application on a brand new PC.
The Too Little is also very tricky since ANY previous NI software installations might have installed the drivers you need in your current app fooling you into thinking you included everything you needed for that app to run on a fresh PC. To verify that I had a totally complete install package I tried completely uninstalling all NI software, reboot, and sometimes it still finds NI drivers. This makes it even more important that there is a reliable way to determine what the installer requirements are. If there is no way to do it in the LabVIEW project environment does anyone know of any external dependency checking software?
Using LabVIEW: 7.1.1, 8.5.1 & 2013

Thanks for the feedback. I've used InstallShield before but I was hoping that NI software would be best at building NI software into an EXE. I figured I was just missing some subtle Installer option.
I'll certainly post up the idea at the IE but it seems like a substantially bigger request than most. Can't hurt to ask though...
Dennis, I did notice the three levels of: DAQmx core > DAQmx core + MAX > DAQmx core + MAX + App Dev Support. Unfortunately, I didn't see a way to determine how much extra disk space each option (or any other option for that matter) would cost. I guess I could build up a simple App with one option checked at a time and dtermine their sizes that way.
Using LabVIEW: 7.1.1, 8.5.1 & 2013

Uninstall option for LabVIEW build applicatio​n

Similar Messages

Maybe you are looking for

Uninstall option for LabVIEW build application