another distribution editor weirdness

[menchar]

When I add the dependencies of an executable to a destination (target) folder, the 8.5 dist editor shows TWO copies of the DLL being placed on the target,

(MyDLL.dll, MyDLL.dll)

and the reported size is, in fact, twice the size of the DLL.

Then, if you putz around a bit and switch to a different window, or restart the dist editor, and you go back and look at that same target folder, it reports only one copy of the DLL, and reports the correct size !?

I have the DLL .prj in the same workspace as the app, with the app as the active project.

If I place that same DLL into the same target folder not as an application dependency but as the target of the DLL project, then the editor properly reports placing both the dll and the import library into the target, and offers to remove the import library as you would expect.

Pretty weird, huh.

I've always hated this distribution editor.

Menchar

[Manooch_H]

Hi Menchar,

Thanks for bringing this to our attention. I have filed a Corrective Action Request on your behalf. The CAR ID is 137318. We will try to get this corrected in a future release.

[menchar]

Has this problem been fixed?  If so, how do I get the fix?  If not, how do I get around it?

How do I distribute the DLL dependencies of an application?  I don't want to make a jillion separate distribution kits.

[Manooch_H]

Hi Menchar,

I actually just validated this fix for CVI 9.0.1 yesterday. With the release of CVI 9.0.1 we should no longer see this problem.

Message Edited by Manooch_H on 02-10-2009 10:32 AM

Message Edited by Manooch_H on 02-10-2009 10:32 AM

[Mert_A.]

Also, note that the problem is cosmetic. The built distribution contains only one reference to the dependency file, and installs just one dependency file. It's not possible that this bug was causing you any run-time problems with your distributed app.

Mert A.

National Instruments

[menchar]

OK.  The way it was looking, I couldn't tell if it was a display problem only, though it did occur to me that might be the case.