2010 user.lib Path in Executable Changed from 2009 (1abvi3w)

[robweaver]

Our group often uses VI server to control other LabVIEW executables to automated testing. To control VIs through VI server in executables and monitor VIs we need to build the full path we're expecting the VI to be at within the executable.

For LabVIEW 2009 user.lib VIs the path used to show up as:

<executable name>.exe\LabVIEW 2009\user.lib\...

For LabVIEW 2010 user.lib VIs (on Win XP AND Win 7) the path now shows up as:

<executable name>.exe\1abvi3w\user.lib\...

This is just an FYI for developers. This really threw a wrench into our VI server calls and are unsure as to why it changed and why its "1abvi3w". Who's the funny guy?

Seriously though, why did this change and why use a "1" and a "3". Is this an attempt at 1337 speak?

[gmart · Accepted solution]

Paths in built applications are based on the source VI's hierarchy. For files in the LabVIEW directory, the actual LabVIEW directory name was being used in 2009. This was ok except when creating builds across platforms or across machines where LabVIEW was installed in a different location. So for 2010, a unique, constant directory name was chosen.

[robweaver]

George,

Thanks for the quick reply. The constant pathing does make sense for cross platform. So I guess my final question is can we expect this to now be the standard for future versions of LabVIEW?

Thanks,

Rob

[gmart]

Barring any unforeseen problems, the directory name should not change.