installer moves files around

[dsavir]

Hi,

I have a program that I am upgrading from Labview 8.2 to LV 8.5. I succeeded in creating an exe file with all the supporting folders (for example - Global.vi is in Scan Control folder). When I try to create an installer, I go to source Files and move the build into the destination folder. When looking at the destination files, I find that the installer has moved the files around (now Global.vi is in the root folder and Scan Control folder is filled with other stuff which are totally disconnected).

How do I change this? Why is the installer moving things around?

Thanks,

Danielle

[LV_Pro]

Are you using "projects" in these versions? I'm assuming you are since I'm pretty sure that the builder now requires it. Check that the virtual folders in the project are actually mapped to their equivalent O/S folders. I'm not sure what LabVIEW does it they aren't as I have tried to use the same heirarchy structure in the project and out, but that sounds like a possibility, or not    Additionally, check in builder to where it says each of the folders is mapped.


Message Edited by LV_Pro on 12-20-2007 08:35 AM

[gmart]

It sounds like your issue may be similar to what is documented here - http://digital.ni.com/public.nsf/allkb/D4C71E1FF52DC9A5862573770071BF10


Message Edited by gmart on 12-20-2007 08:43 AM

[Bob_Preis]

---

@dsavir wrote:

Hi,

I have a program that I am upgrading from Labview 8.2 to LV 8.5. I succeeded in creating an exe file with all the supporting folders (for example - Global.vi is in Scan Control folder). When I try to create an installer, I go to source Files and move the build into the destination folder. When looking at the destination files, I find that the installer has moved the files around (now Global.vi is in the root folder and Scan Control folder is filled with other stuff which are totally disconnected).

How do I change this? Why is the installer moving things around?

Thanks,

Danielle

---

Hi Dsavir,

I replied to your other thread about the installer builder problem with a zip file that I'd like you to try. I'll post it to this thread as well. Basically just unzip the two files into vi.lib, backing up the originals first of course.

[dsavir]

Hi,

I replied also on the other thread, but if someone comes across this one - these files solve all the installer problems I'd been having: files moving around and problem running an exe after the installation.

Thanks a lot, Bob!

Danielle

[dsavir]

Hi all,

Unfortunately, the problem has returned...

When building the application, everything is fine and the preview is the same as what I actually get.

When attempting to build an installer, in "source files" the files from the build are incorrect - it adds an additional empty folder called "config data refnum" and then refuses to build the installer because it cannot find this folder.

 I recopied the vi.lib.zip files that Bob posted and it didn't change anything. I built a new builder and installer from scratch - nothing.

Does anyone have any idea what could be the matter now?

Thanks,

Danielle

[Bob_Preis]

---

dsavir wrote:

Hi all,

Unfortunately, the problem has returned...

When building the application, everything is fine and the preview is the same as what I actually get.

When attempting to build an installer, in "source files" the files from the build are incorrect - it adds an additional empty folder called "config data refnum" and then refuses to build the installer because it cannot find this folder.

 I recopied the vi.lib.zip files that Bob posted and it didn't change anything. I built a new builder and installer from scratch - nothing.

Does anyone have any idea what could be the matter now?

Thanks,

Danielle

---

Danielle,

So on the Source Files page, are you seeing the additional empty folder on the left-hand side (Project View), or on the right-hand side (Destination View)? This one sounds different from the other issue if the problem is on the Project View. It might be worthwhile adding CDK.EnableLog=TRUE to your LabVIEW.ini. This will generate a log file which could give us some additional clues (assuming the build isn't haulted before the logging mechanism kicks in). Also, if you have a simple way to reproduce the problem, perhaps you could attach the sample here for further investigation. Another idea is to grab the 8.5.1 patch and try it before really digging into it. Let me know what happens, thanks.

-Bob

[James_G1]

I am seeing a similar issue with LabVIEW 2009 SP1.  I have created an exe.  Now I want to create an installer.  This program is one of several demo programs that can each be loaded onto the machine or not.  I thought it made sense to have a folder under the [programfilesfolder] called indy demos, then put this demo in that folder.  This is causing problems, It seems that if I want to put the whole thing in [ProgramFilesFolder]/indy demos/indy demo feedback it automatically moves the data folder up a level.  Strangely it leaves an empty data folder where it is supposed to be but the dlls got moved up a level.  As a result when I run the installer on the target computer then run the program it is not able to find the dlls.

Why it is doing this?  Am I violating some conventions?  Can I change this behavior?

James

[James_G1]

Here is a screen shot showing my configuration.  You can see the empty data folder and the moved data folder with the plus sign next to it.  In the project view you can see that this is not my original file layout.  I can't seem to stop it from moving these files around.

[JordanG]

You should check your desination settings. Are they relative to one another and relative to what you would expect? Have you tried Bob's suggestion of adding CDK.EnableLog=TRUE to your LabVIEW.ini? This log file might help identify where the problem is occuring.

Jordan