Analyze Source Files works not properly

[baloss]

Hello everybody,

I want to deploy a TS sequence with TS 4.0.

The sequence includes both CVI and LabView modules.

The first time I deployed the system (from a TS Workspace file), the "Analyze Source Files" tool identified correctly the VI used by the sequence, and added them to the files to distribute. 

The deployment was successfully generated, and I saved the configuration (.tsd).

Then I modified my sequence adding a VI which wasn't previously used.

When I tried to deploy the system again (with the configuration saved previously), I noticed that the "Analyze Source Files" didn't add the new VI. (Remark: I saved the sequence and the workspace before start the deployment tool)

Is there something wrong in my LabView Options settings? (I didn't modify the default settings).

Note:

The VIs mentioned are from an agilent driver library downloaded by NI site.

Any help would be appreciated

Thank you

Baloss

[Johann.Wagner]

by configuring and adding the files the first time you say relative or absolut path. I suppose that when you want distribute the application again teststand don´t find the files in right path and therefore no detection. Do you try with rightclick to project and add files a new importing and analysing of a sequence with labview/cvi files ?

Best Regards

AE Munich

[Johann.Wagner]

Please send me your project (workspace) here because i can´t reproduce the problem. Have you test it also with other TS Version (30 days evaluation without activation) ?

You can add with rightclick on project folders and files - so you can add additionally the files and test if TS can find/analyze these.

[Johann.Wagner]

Have you test it also with other pc ? Sometimes a new installation helps. Deinstall it with msiblast.exe (find on ftp.ni.com/outgoing/) and install new...

[baloss]

Hi Johann,

thank you for your suggestions. Sorry for my late answer but I take some sunny week holidays...

Meanwhile my collegue (working on the same project) has decided to replace the VI agilent driver with the corresponding CVI code.

Now everything works fine, but of course the TS only call CVI modules.

About new installation: we worked with the same PC, deinstalling the code with Windows tools ("Control Panel"-> "Add or Remove SW")

Thank you

baloss