LabVIEW
AF Project Loaded in LV 2017 Has New Dependencies
I have opened my Actor Framework based application in Labview 2017, and I noticed two new dependencies that weren't there in 2016, which are the ones pointed to with red lines. They both seem to be there due to some call that eventually resolves to Do.vi (and in one instance, it points to a case where I am using the LV Config file VIs for reading a config file).
My plan is to just continue on with my work, I was just surprised by it, and hope nothing else is broken. Unfortunately I can't make my code available for inspection, though I am trying to pare it down to pinpoint where it is coming from, and why the VI part isn't contained in vi.lib.
And I think I just found it. The Actor Framework VI "Read Error Report.vi" when added to the block diagram creates both of those dependencies it seems. Not sure if this is a bug or not, but thought I would point it out in case someone else looks for it.
