"Application Directory" Function Sometimes Breaks

[paul_cardinale]

This problem occurs in my giant app, but when I pull out the problematic code (attached) and run it separately, it works fine.

When I drill down (from the real app), I find that "vi.lib\Utility\lvfile.llb\Is File an LLB.vi" claims to be part of "NI_File Type.lvlib" but that library does not claim to own it.

Here's how the problem shows up:  I have a static reference to a VI, from which I get its path.  I open a (strictly typed) reference to it in an alternate application context.  But it's broken in that context

Drilling down through the subVIs, I find that the built-in function (really a .vi) "Application Directory" is broken.

It's further down under that* where I find that "Is File an LLB.vi" is broken.

I'm suspecting it's due to instances of various things open/running in various contexts, but I can't track it down.

* Yeah, I know I'm not supposed to go there.

[pauldavey]

Is the error occurring in the development environment, or the run-time?

[paul_cardinale]

---

@pauldavey wrote:

Is the error occurring in the development environment, or the run-time?

---

In the runtime enviroponment.

[paul_cardinale]

It turns out that in the real app, depending on what project it loads into the alternate context, there may be trimmed down copies of .lvlib files from vi.lib.  And the "Application Directory" function has dependencies that could be missing in that context.