02-24-2012 08:43 AM
Thanks, it still a probelm and I've tried many things and I can't recall if I performed these exact steps, so i will give it a try...
12-15-2015 03:11 PM
I was recently searching to see if anyone else had beamgage+labview experience here, and ran across this old post.
I don't know if you ever resolved your issue, but Spiricon recently released a new version of beamgage (6.6) that included a major overhaul of the .NET engine.
One issue that still remains is that you must place your labview compiled executable in the same folder as the beamgage exe and all its DLLs.
Spiricon claims this is a labview runtime engine quirk.
Anyway, I was able to run compiled labview code following this recommendation.