distribution kit between 8.01 and 8.1.0

[GarthE]

Hi,

I am using:

OS: Windows XP

CVI: 8.1.0 and 8.0.1

I built a distribution kit with version 8.0.1 on one computer, and then tried to build the distribution kit from a second computer running CVI 8.1.0, and the distribution kit settings were incomplete.

I checked the build settings on both computers, and both point to the same cds file.

The distribution kit when opened on the second computer retained the locate where the distribution kit should be built, the shortcuts I created, and the folder structure, but the dlls, exes, and config files that were in the folders are not present in the distribution.

The location of the exes, dll, and config files are the same on both computers.

Any ideas?

C:\Project\

                 Bin

                 Config

                 Report

                 ..........

Thanks,

Garth

[Mert_A.]

Hi Garth,

When you say that the files are "not present in the distribution," do you mean that they are not installed by the built distribution, or that they do not appear in the tree view of the Edit Installer dialog's Files tab?  If the latter, do the directories you created appear?  Are there any items that appear with red filenames?  Usually, if there are files referenced by your distribution that cannot be located (which can sometimes happen when moving a project/distribution from one filesystem to another), then the referenced files will still appear in your distribution hierarchy, but any missing files (or directories containing missing files) will be shown with red filenames.  If the items do not show up at all, then there is something wrong. Maybe changes to the .cds were not saved, or some other unexpected issue.

Could you post your .cds file?

Thanks.

Mert A.
National Instruments

[menchar]

You have to watch out for hard links to specific folders for some files in your distribution.  Are the files in red font in lower right hand pane of the distribution editor?

You can aribitrarily add files to your project, the links to these will relocate with the project, and the distribution editor will find them.  If you add a file directly into the distribution, but not the project, it will have a hard link to the file location that will not relocate when you move the project.

You often discover this nuance when you first try to create a distribution after moving your project to a new folder or a different machine and the hard links get broken.

Not clear that this is what's happening to you but it's worth checking.

It would be nice if the distribution editor could flag file links as being "hard links" or "soft" (relative) links so that you don't get an ugly surprise when you go to recreate a distribution after moving the project only to find a bunch of files can't be found.

Even more insidious is if you've rev'd your application, and the old rev folder is still present - then the dist editor finds the old folder and pulls in files from there, not from your new folder  You can right click the filename in the dist editor file panel to see the full path.  I've shown this to several developers - much to their surprise they were not distributing the files they thought they were!

As a separate issue, the dist editor is a royal PITA to use because the panel / panes are so small and can't be re-sized.    You also can't import registry files - you have to tediously build up any registry trees you want to use. 

That distribution editor needs some improvements IMHO.

Menchar.

[Mert_A.]

If the relocation semantics are a concern to you, I would suggest getting in the habit of explicitly adding files you distribute to your project (in the project tree).  This should avoid relocation issues, even if copies of the files still exist in the original location.

You might be interested in updating your version of CVI, though.  We took note of your .reg file import/export suggestion, and it is part of the CVI distribution builder as of version 8.1. It is in the right click menu of the registry tree of the Edit Installer dialog ("Export Branch", "Export All", "Import Branch").  Also, the distribution dialog will be significantly larger in the next version of CVI, so as not to feel so cramped.

Ask and ye shall receive. (If we agree, and can fit it in our schedule.)

Mert A.
National Instruments

[menchar]

Dang, I'm flattered

I haven't been running 8.1 much because one of our primary products won't work with the CVI 8.1 RTE due to what I think is a poorly imlpemented serial port in an FPGA. 

Now if I could get the dist editor to be able to load a specific version of the RTE into the dist kit, I could develop/build in 8.1 and distribute the 8.0 RTE ...

Menchar

[GarthE]

Thank you both for responding quickly.

Mert I am posting my cds file.

I will try and make things a little clearer.

All the project files, workspaces, cds files, and source code are kept in clearcase.  The same exact workspace is opened on each computer.

The workspace when compiled builds all executables into:

C:\PROJECT\Bin

on both computers.

You will notice looking at the cds file that all the paths to the executables are fully qualified.

The files are missing from the file list when editing the distribution kit.  The files do not show up in red in the lower right hand corner.  I know I am opening the same cds because all of the other information is the same, and the path to the cds file is displayed when you click on manage distributions.

I tried editing the file paths to be relative manually using a text editor but this caused the working distribution to break, and the file did indeed show up in red.

Thanks,

Garth

[Mert_A.]

Garth,

I'm sorry I didn't have an answer for you quicker, but it turns out this is a known bug (459H7S0S) introduced in version 8.1.0 and fixed in 8.1.1.  You can download version 8.1.1, and since it is a maintenance update to version 8.1.0, you can activate it with the same license.

Alternately, as a workaround, you can avoid the problem by adding a project output or project dependencies item (see screenshot) to your distribution. Even if the item does not actually represent any real files (as is often the case with the project dependencies item), it will prevent your other files from disappearing. You'll have to add the item in version 8.0; by the time you load the distribution in version 8.1.0, your files are lost.

Sorry again for the trouble.

Mert A.
National Instruments


Message Edited by Mert A. on 11-08-2007 11:47 AM

[wally_666]

I've stayed with CVI 5.5 since I find the distribution kit builder has been in a downward sprial starting with CVI 6.0.

Recently upgraded to CVI 8 for the linux runtime support and all I can say is what were you thinking with this current dist kit builder and installer?
I don't see a single benefit to it.

--wally.

[Mert_A.]

The main benefit is the capability to (often automatically) bundle drivers and runtime components alongside your application into one installer. There are many other new features including better versioning, more configurable shortcuts and file options, registry key installation, launch conditions, and a more customizable installer UI.

Some users have expressed frustration at the increased size of the new installers, or at having to refamiliarize themselves with the UI. Is there something in particular that you dislike about the changes?  Are there other features you could suggest that you would find more beneficial?

Mert A.
National Instruments

[NicoLeach]

I would be very pleased with the installer provided with CVI :
*if it change towards Wix or NSIS
*or if it stopped changing so I won't have to change my workarounds a each new version (It was the case between 7.0 and 7.1 and between 7.1 and 8.0)

Nicolas