From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
05-08-2012 10:17 AM
Hi all,
I'm upgrading a large app from LV 7.1 to LV2010 and it turns out that more than just a few VIs are calling property/invoke node that are now deprecated (they appear in red instead of yellow).
When I come across one one them I modify the node to use the corresponding new property/method but I could easily miss some of them.
So is there a way of getting the list of all calls to deprecated property/invoke nodes?
Thanks in advance for any help
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
05-08-2012 11:02 AM
Check VI Analyzer. If I recall correctly, it has a test for finding deprecated properties/methods. I might be wrong, but I think so.
05-09-2012 03:52 AM
Indeed! thanks for the pointer!
http://zone.ni.com/reference/en-XX/help/371361G-01/lvvianalyzerhelp/general_tests/
>>
The tests in the following list analyze the overall setup of a VI.
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
05-09-2012 07:09 AM
If that fails, let us know. There are some private methods to determine whether or not a property or method node contains deprecated items. If you need them, I can track down whether or not I can release VI-wrapped versions of them.
05-09-2012 07:39 AM
Hi,
It didn't work it only point me to properties that can't go into an exe but it will skip those that are deprecated. For instance in the VI below the report would only point me to the "AssignCtrlToTerm" node and not to the "Create Constant or Control" node (that is now replaced with the "Create form Reference" I assume)
Oh, and would that work?
Cheers
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
05-09-2012 10:23 AM
I can post VI-wrapped versions of the internal methods. What version of LabVIEW do you want them in?
05-09-2012 10:34 AM
2010, 2011and to 2012b if possible please.
Thnaks a lot!
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
05-09-2012 01:35 PM
Here you go. These are written in LabVIEW 2010, and have locked block diagrams, but will upcompile to 2011 and 2012 with no problems. Let me know if you run into issues.
I would probably use them to find deprecated nodes as follows:
05-10-2012 01:39 AM
Thanks a lot, I'll try it out and let you know!
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus
05-10-2012 02:51 AM
Oh.. and one question, what would you use in LV 2010 to replace the VI property node "Callees Paths"?
thanks in advance
We have two ears and one mouth so that we can listen twice as much as we speak.
Epictetus