RTEhasObjCacheAccess in LV 2013

[jeff.kittle]

I'm trying to run vi plugins from an exe.  To do this in previous LV versions (2011) you had to add RTEhasObjCacheAccess=TRUE to the exe .ini file.  This does not seem to work in LV 2013.  Is there a change to this feature?

[I.B.Hating]

Hi Jeff,

What plugin are you trying to run from your exe?

[Jeff-P]

You can dynamically call VIs from an exe without using that token. Check to see if the VIs you are dynamically calling have separate compiled code enabled, it should be disabled on VIs that you are dynamically calling (VIs distributed with an exe or in a source distribution). The token you are referencing requires the presence of the development environment on the same computer as the exe.

Regards,

Jeff Peacock 

Product Support Engineer | LabVIEW R&D | National Instruments | Certified LabVIEW Architect 

[jeff.kittle]

The token is required because in 2010 (I think) NI seperated the object code from the vi's in vi.lib.  So you can make it work without the token if you don't use anything from vi.lib.

I did get this token to work on a simple example I had put together when using LV 2011 and now converted to 2013.  However, my larger application I'm using this in is not yet working with the token.  I think I may have to add additional search path tokens.

Here are the current tokens I have to add to my .exe's ini file:

libdir=C:\Program Files (x86)\National Instruments\LabVIEW 2013
RTEhasObjCacheAccess=True
viSearchPAth="C:\Program Files (x86)\National Instruments\LabVIEW 2013\vi.lib\*"

[Jeff-P]

You are correct that vi.lib has the compiled code separated from the VIs. You can still dynamically call VIs that make use of vi.lib as long as you make a source distribution of those VIs. You could build your plugins into Source Distributions and under Additional Exclusions in the build specification settings you can uncheck the box to Exclude files from vi.lib and make sure the Remove compiled code option is unchecked as well. This includes the relevant vi.lib VIs with their compiled code. This is the recommended way of doing what you are trying to do, and it has the added benefit that you don't need the development environment on the computer to run your plugins anymore. 

Regards,

Jeff Peacock 

Product Support Engineer | LabVIEW R&D | National Instruments | Certified LabVIEW Architect