Serious problem with old versions of sub-vi's installing on application upload

[Ashley.w]

Hi

I am having a series problem which is proving wildly frustrating.

I have recompiled an application but when I upload it on the host computers the host computers seem to upload old versions of the code even though they have been deleted.

I smell a Windows Cache problem but can't see how to get round it.

Anybody have any ideas.  If not should I shoot myself before or after I get fired?

Either way help appreciated

Ash

[tbd]

Hi Ashley,

      I've been compiling and deploying LabVIEW applications for a long time, and never seen a windows-cach problem!

Here are a few (of my) mistakes that resulted in execution of old code:

Forgetting to update the Top-level VI in the .bld, after the top-level VI's location changed.

Compiling to a different location than the one I copied the "new" EXE from.

Compiling with Installer option, then switching-off Installer option (for faster compiles), then, post compile, instead of copying new EXE - doing an Install and installing old EXE!

After copying or installing new EXE to host, forgetting to update menu-options and "shortcuts" - which still point to old EXE.

Some ideas:

Write a new/unique version# to the Main VI's Window Title (VI properties), so you can tell quickly which version is running.

After compiling, pay close attention to the creation time of the "new" EXE to be sure it is new.

After copying or installing, launch the new EXE by double-clicking on it (don't trust existing shortcuts.)

Cheers!

[Ashley.w]

Hi Tbd

Thanks for you reply.

I shall pay attention to your tips.

apologies if my post was a bit stress laiden.  I have been on some very tight deadlines recently. 

Thanks again

Ash

[tbd]

Deadlines?  See fourth quote here!