03-15-2023 08:13 AM
I've built this app many times; this is the first time for this error.
When I run it, I get this:
If I browse to that in in vi.lib, I get this:
I understand the 2nd error message, but not the first. What could cause the dependency on "Get Type Information.vi" not to be included in the build?
03-15-2023 08:25 AM
The first error is related to the this property of the VI:
this can happen when your executable is calling a VI, but it has removed the compiled code.
03-15-2023 09:22 AM
@petrz wrote:
The first error is related to the this property of the VI:
this can happen when your executable is calling a VI, but it has removed the compiled code.
No, that's the 2nd error, not the first.
Furthermore, the VI with separated code is in vi.lib; it hasn't changed, and the build use to work.
03-15-2023 11:25 AM - edited 03-15-2023 11:27 AM
I'm sure you've tried all sorts of things already but a few questions:
1- Have you cleared the compiled object cache? It could force the recompile.
2- Have you tried "cleaning" the build? (Right click -> Clean)
3- Could you delete and replace that function? Maybe one instance in one VI got corrupted somehow.
4- Any chance you're calling that VI dynamically, and the linking got weird somehow? (I only ask because dynamically calling a VI in vi.lib seems like something @paul_cardinale would do to accomplish something sneaky 😉)
03-16-2023 02:04 AM
Sorry I misunderstand it, I tough you're referencing to a VI in our library, now I'm realize that it is VI from the vi.lib
Clearing the VI cache is good idea, but I think for the VIs in the vi.lib the cache is located in VIObjCache (e.g. C:\Program Files\National Instruments\LabVIEW 2018\VIObjCache) it has to be cleared manually.