Is it possible to subpanel a vi from another application instance?

[sdusing]

I have a vi I'm running from TestStand, and it's loading in a different application instance than my LabVIEW app.  I know how I can get them on the same application instance, but that creates other problems for me. I'd really like to be able to have my LabVIEW app subpanel a vi that is running in another application instance, but I don't think it's possible. I'm hoping someone can confirm or comment on if there are any known workarounds.

[paul_a_cardinale]

Just try it and see if it works.

[sdusing]

I have tried it - it does not work, which is what I should have said when I mentioned "I don't think it's possible". I ask the question because I am wondering if there are any other tricks or workarounds.  Otherwise it sounds like it is a requirement that a vi be in the same application instance to subpanel into another. I'll accept that, just wanted to verify that conclusion with community experts.

[paul_a_cardinale]

I just threw together some code.  It works OK for me.

[sdusing]

Really!? would you be able to share it?

[santo_13]

So, you want to see the FP of a VI running in another application instance (TS)?

Why is this a need?

[sdusing]

When running from the development environment in LabVIEW (a project application instance), I would like to subpanel vi's that are run from TestStand (in the default application instance) to provide a more integrated application experience.

At risk of going down a rabbit hole here, I'll mention I'm aware of a couple of workarounds, but they cause other notable painpoints:
1. Create plugin vi's for subpanelling into the LabVIEW application that interface with the Teststand code through UI messages or another means. This is quite a bit of extra work I'm looking to avoid.
2.  run the LabVIEW project code from the main application instance.  To do this you either need to avoid opening an lvproj file which removes lots of useful IDE capabilities or you open the lvproj file and switch your top level vi's application instance to the default (main) application instance.  However, when you do this, it locks up classes since they're now open in two application instances (the lvproj app instance and the default/main app instance).  Even after you finish running your code, LabVIEW never fully unloads the classes from memory, which is a known limitation/feature of LabVIEW.  Locked classes limits what you can then do with your code after you run once and you need to close and reopen your project to unlock the code.  This is the painful workaround I'm currently dealing with.

[paul_a_cardinale · Accepted solution]

---

@sdusing wrote:

Really!? would you be able to share it?

---

Here

[sdusing]

I learned something new today. Thank you Paul!

[sdusing]

Just wanted to show the test I was able to run and how I did in fact confirm this functionality. VI that is subpanelled is running in the main app instance. The vi on the left is running in the project app instance. Opening the vi by name in the correct app instance did work and did allow me to subpanel it into another.