LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

About installer

Hello,
 
I'm using CVI 8.0. Here is a question about the installer.
My project is in a directory, lets call it MyProgram1. I have created a distributuion kit for that program which is working fine.
 
Now I want to add some new features to my program. In order not to destroy my first program, I copy the hole project from directory MyProgram1 to directory MyProgram2, load the project into CVI from MyProgram2 and add the new features.
 
When I wanted to create a new distribution kit for my second program I saw that all additionnal files I had added were still referenced from directory MyProgram1. So I had to delete them and add them again from the new directory. As these files are quite numerous its a long job which can introduce a lot of errors. This behaviour is different from the installer shipped until release 7.1. So I'm wondering how to avoid that. Have I to add all files to the project tree in CVI ?
 
I hope my explanation is understandable.
 
Thank you for your help
Bertrand
0 Kudos
Message 1 of 4
(3,216 Views)
Hello Bertrand,

Unless a file is a member of the project, we assume that its location on disk is fixed.  If you have copied of all the files to your new MyProgram2 directory in order to preserve the originals, then it seems to imply that the files are indeed not shared, but rather owned by the project instance.  If this is the case, it probably makes sense to add them to your project.  If you do this, then they will be referenced relative to the project, and you won't have this problem in the future.

I hope this helps clear up the logic behind the behavior.

Mert A.
National Instruments
0 Kudos
Message 2 of 4
(3,205 Views)
If you find yourself in this situation again, you can normally edit the .prj file in notepad.  Search and replace can be a lot faster than updating a long list of files in a project.

Message Edited by mvr on 05-23-2006 01:15 PM

0 Kudos
Message 3 of 4
(3,202 Views)

Thank you for your inputs.

At the end the easiest way I found to solve my problem was to edit with NotePad the .cds file created by the installer and replace the old path to the files by the new one.

Bertrand

0 Kudos
Message 4 of 4
(3,171 Views)