GetValueByPointer difference between LV2011 SP1 and LV2012

[vix]

Using LV2011 SP1 I developed an application where I successfully used GetValueByPointer.xnode (see here) both while debugging it and while executing it as a standalone application.

After I upgraded to LV2012 the application works fine while debugging it, but not as standalone application.

After some investigation I found that xnode code has changed from LV2011 SP1 to LV2012 (see snippets).

Why this code has been modified?

How can I get my application working in LabVIEW 2012?

[vix]

I forgot to add that running as standalone, the application doesn't work because it isn't able to find the lvimptsl.dll library;

and I think this is a problem of path

[bronzacuerta]

Hi

the GetValueByPointer generated code makes a call to lvimptsl.dll, which is in the resource directory.  Since resource is not in the search path, moving a VI that contains GetValueByPointer from one version of LV to another will not update the version of the DLL that is used. 

This problem could also be related to RunTimeEngine.

Install

<http://joule.ni.com/nidu/cds/view/p/id/3582/lang/en>

or

<http://joule.ni.com/nidu/cds/view/p/id/3588/lang/en>

and try again!

Let us know!

[vix]

I had already installed the LV2012 f3 patch, but I think this is not the problem.

As a matter of fact the behavior is different even if you create projects from scratch.

[vix]

CAR 380809

[wolfeman]

I am having simmilar problem? Any word on cause / fix?

[wolfeman]

Actually,

The problem is in the development env everything works as advertized; but in the compilied binary the call to "getvaluebypointer" doesnt come back with any data at all....

This worked fine in LV2011 and earlier version - the only change was to 2012 and it broke...

Any help or hints would be appreciated...

Thanks

[vix]

Hi

as I wrote, this has been recognized as a bug by NI, and CAS 380809 has been filled.

Unforntunately this will be fixed in one of the future LabVIEW releases.

In the meanwhile you must:

1. add lvimpts.dll to the project files (so that you can see it in Build specification >> Exe)
2. modify the Build Specification >> Exe so that a new subfolder called "resource" is created as destination
3. include lvimpts.dll inside "resource" subfolder

Hope this helps

[wolfeman]

Ok thanks,

I did get it working, but I manually "recreated" the old way by converting the xnode calls to a static vi dll call, that mirrors the 2011 method.  

[ChrisLudwig]

This is an old thread, but I ran into the exact same problem in LV 2014.  Guess this very simple bug is still not fixed.  The provided work around did the trick.  I searched within my Labview install folder for lvimptsl.dll and copied it into my project folder and then drug it into the project explorer and placed it next to my VI:

I then opened the build specification properties and set the dll as always included:

And then changed the destination path to "resource":

I rebuilt my application and all works now.

Thanks for the work around and Kudos to you.