So in a nutshell, this is how my real application works (All running using LabVIEW run-time and TestStand Base Deploy:
- Splash.exe Launches Vis to run in background via VI-Server calls
- Splash.exe Launches TestStand in Background
- Splash.exe Launches MainApplication.exe
- MainApplication.exe runs
- Launches TestStand sequence to execute based on configuration data pulled
- Launches Vis dynamically to run embedded in its panel window
- TestStand Sequences running
- Makes calls to dynamic Vis running in background (launched via splash.exe)
- Updates TS status/progress to MainApplication.exe UI
Because I'm making dynamic VI calls on VIs that are shared between TestStand and LabVIEW Run-Time I couldn't use source distribution or directly add all the dynamic VIs to the .exe build; NOTE that there's at least 25 vis here that are dynamically called from my exe and shared between .exe and TestStand, adding to the build breaks the ability for them to be shared because TestStand "can't find the VI's" when they're pulled into the .exe...
I was able to bypass these suggested methods simply by adding JSON and HTTP source VIs to be included in my exe build.
Strange part is I didn’t think it would work because of how I’m dynamically calling the Vis from TestStand and the potential to make them not found by including in the exe, but somehow this seems to work just fine...
Search LabVIEW like a graph! 
