Leaderboard

I had a brief look at Orleans last night. Very interesting, but it brings up a warning. Most “actor” programming out there has been developed to handle distributed software-only applications on large numbers of interchangeable servers. Think 20,000 Halo5 players and 2 or 3 Microsoft server farms. We, in LabVIEW, are more likely to be dealing with a small number of not-at-all-interchangeable pieces of physical hardware. We don’t have the option of handling an error by restarting to finish the job on a different server. So the features of Orleans “virtual actors” sounds very interesting, but not necessarily that applicable to hardware-controlling applications. I would still look at Akka if I were not doing LabVIEW.

Thanks I'll have a look at this over the weekend. EDIT: I did have some look at this and got the newer code to work a bit more, but need to test on a real x64 cRIO system. Hope to get my hands on one during this week.

The LabVIEW PDA Toolkit is not supported anymore as you may know and that is the only way to support Windows CE platform. That said, labview.lib basically does something like this which you can pretty easily program yourself for a limited number of LabVIEW C functions: MgErr GetLVFunctionPtr(CStr lvFuncName, ProcPtr *procPtr) { HMODULE libHandle = GetModuleHandle(NULL); *procPtr = NULL; if (libHandle) { *procPtr = (ProcPtr)GetProcAddress(libHandle, lvFuncName); } if (!*procPtr) { libHandle = GetModuleHandle("lvrt.dll"); if (libHandle) { *procPtr = (ProcPtr)GetProcAddress(libHandle, lvFuncName); } } if (!*procPtr) { return rFNotFound; } return noErr; } The runtime DLL lvrt.dll may have a different name on the Windows CE platform, or maybe it isn't even a DLL but gets entirely linked into the LabVIEW executable. I never worked with the PDA toolkit so don't know about that.