Messaging to A Packed Project Library (PPL)

[Parker-JET]

Hi all, 

For some context on the project:
I am working on a codebase right now and we are running into issues with messaging to a PPL that we are launching. We are using the PPL for plugins on the codebase. 

The goal of what we are doing is to run tests on the main codebase with a plugin. We planned on going about doing this by sending messages back and forth to communicate the necessary information for testing. 

The issue that we have ran into is that it appears the PPL is running in a different application space when launched from the software. I am checking this with some debug dialogs giving out the application reference in hex.

Are there ways to launch the PPL in the same application space? 
Are there ways to communicate with the PPL other than the usual intra-application communication such as TCP or shared variables?

I am currently going around the issue by messaging through some temp binary files. I don't like this approach, but we need a solution in a timely manner.

[Kyle97330 · Accepted solution]

There's two ways that I believe should work.

One is that you create a PPL that controls all messaging, and have both your main application and other PPLs call VIs from that.  If all messaging goes through that, then it's all in one "application space".

The other is that I have found that named queues are accessible by all application spaces.  You'd need to coordinate both the names of the queues as well as being sure that you don't use type definitions inside the data definition of those queues.  See this thread from a while back:

https://forums.ni.com/t5/LabVIEW/Named-Queues-in-VIs-Launched-by-VI-Server-Some-Work-Some-Don-t/td-p...

[Parker-JET]

Thank you for the response. 
We attempted to do Named Queues but we were using type definition as the data element.
We were looking for errors to be thrown by the queue create but were not seeing any so we were thinking it was not going to work.

I removed the type definition and the named queue passes data.