LV8.5.1 Installer builder bug?

[Slyfer]

Hi,

I experienced this strange behaviour (see image attached).

I build 2 exe files, they are OK. When I try to build an installer Labview scrambles the POSITIONS outside of the selected path for installation.

This invalidates the installer, because it's all a mess and in the next tab I am not able to properly set the links and so on.

Is there something wrong in the building process of the executables?

I tried everything, creating the project from scratch and re-doing step by step, but cannot figure out what to do

Using Win xp pro sp3, LV 8.5.1

Thanks

Message Edited by Slyfer on 10-29-2008 09:27 AM

[Andrey_Dmitriev]

Hi, Slyfer,

As far as I can see you have two build specs and one common installer for both applications.

For me nothing wrong - all seems to be OK, as expected (checked both LV - 8.6 and 8.5):

Simple test project in attachment.

Andrey.

Message Edited by Andrey Dmitriev on 10-29-2008 12:06 PM

[Slyfer]

In the same PC, I have installed every Labview (6.1, 7.1, 8, 8.2, 8.5, 8.5.1 which overwrited 8.5, and 8.6), I use professional version.

Could it be that? 

The project was using some Virtual folder that does not match the original tree in the  system, but this is what "virtual" folder are made for.

Maybe the installer is messed up by this mismatch?

[Andrey_Dmitriev]

I don't think that this caused by interference with different versions (I also have multiple LabVIEWs installed).

What you can do is following - open the *.lvproj in any text editor and see where your applications inserted into installer. They inserted by GUIDs, and I guess, that something wrong here. If you want to have both applications at the same location, then they should be pointed to the same GUID:

Or just post your simplified project here.

Andrey.

Message Edited by Andrey Dmitriev on 10-29-2008 12:39 PM

[Slyfer]

I checked the proj file with "XML Notepad 2007".

I think it's ok, the property "#text" is the following string:

{1C842053-B3EB-4F54-9EC8-DDCAE5CC2794}

This string appears (verified with find function of the editor) in the XML tree under the following nodes:

DirInfo.DefaultDir

DirInfo[0].DirTag

FileInfo[0].DirTag

FileInfo[1].DirTag

FileInfo[2].DirTag

FileInfo[3].DirTag

FileInfo[4].DirTag

FileInfo[5].DirTag

ShortcutInfo[0].FileTagDir

ShortcutInfo[1].FileTagDir

I have a total of 6 files (2 exe, 2 ini, 2 aliases), all should be put in the same directory (that is also default directory). It seems consistent, but again in the "GUI" of Labview, I see the second group of files (exe, ini, aliases) put OUTSIDE of any category.

If I futher add executables, they are put almost randomly, for example "exe" in the correct target dir, "ini" and "alias" outside.

When I save the project file, the XML notepad is updated (it ask "the file has changed, wanna reload?"), I reload it, and I can see that the proj file is CORRECT! but there's something wrong when Labview read it and display it over its GUI.

In the "Source File Settings" category of the installer, the "scrambled" files are outside of [ProgramFilesFolder], and all the controls on the right (file attributes) are grayed.

The "Shortcuts" category is not consistent in the GUI, it shows "MyExe" and "MyExe1" (it appends "1" to the name instead of typing the correct name of the second exe file).

Any ideas?

thanks

[Ben]

This KB discusses an issue that sounds similar to yours. You may wan to take a look at that.

Ben

[Slyfer]

---

NI KB wrote: 

If you are having problems building an application with LabVIEW classes due to incorrect filenames appearing in the Destination View, you will need to make changes to the application's build specification (as opposed to the installer specification). Make the following changes to the build specification to resolve the problems:

• Open the application's build specification and navigate to the Destinations page.
  
• Add a new destination for each class that includes duplicate file names (override VIs).
  
• Go to the Source File Settings page and configure each class (and its files) to go to a unique destination.
  
• Rebuild the application and reconfigure the installer build. You will only need to complete this process one time. 

---

I don't use classes. The executable files consists of 2 vis. The main VI is simply a "launcher", it dinamically load the second vi, it loads strings for localization, runs and opens front panel, then it quits itself (and you have the second vi running) .
The second VI was "always included" in the build specifications 

I modified the build specifications, and now every exe goes into a different folder (previously they targeted the same folder) and the second VI is no longer into the "always included". I rebuilded the application
 

---

NI KB wrote: 
To fix the other issues, you will need to make changes to both your application's build specification and installer specification. In the case of adding shortucts, or registering COM objects, you can work around the problem by removing these files from the Always Include section of your build specification, and instead add them from the Source Files page of the installer build. This work around creates an incomplete application since you may be excluding files needed by the application in the application's build specification. The excluded files are then included by the installer so that when installing your application, all files are placed on the target computer correctly. Because you may need to distribute your application without an installer, National Instruments recommends making a new build specification for this workaround. By having the two specifications, you will easily be able to create a complete application as well as a complete installer for the program.

---

 It is not possible in my case to "add them from the source files page" of the installer, because all I can see are the builds-tree each with exe+aliases+ini files (grayed out). I think this note does not apply to my case.

[Andrey_Dmitriev]

Hmm...

Interesting, the project from second message is also "damaged" on your PC or not?

Another idea - do following:

- create new project

- create and add two VIs to this project - for example, Main1.vi and Main2.vi (both are just empty)

- add two applications specs to the project - App1.exe (Main1.vi is startup VI)  and App2.exe (Main2.vi is startup vi)

- add installer spec and then add both applications to the installer (see if you have "damaged")

- post this "damaged" project here and we will try to reproduce it.

I guess, something wrong with GUIDs on your PC. Some interferences between newly generated GUIDs and system GUIDs or something like that.

Andrey.

[Slyfer · Accepted solution]

The problem was solved.

I made a new project, and I don't know why but now it's working. Either with simple example and with my original VIs.

I didn't use "duplicate" (maybe that messed up), I was always using "new application", "new installer" and so on.

The old project is still bugged. If I open it, it still has the bug.

I don't know where is the bug, but there is something wrong. As of now, the solution is only to re-do the project from scratch.

It's difficult to replicate the problem, and I cannot say if this is solved in LV 8.6. As of now LV 8.6 is working (but I don't make installers all day long...). 

Thanks