Deploying Actors (classic PPL/Build concerns, sorry if a repeat)

[NeilA]

🙃 oh my goodness, you had me dead to rights, straight away missed the move, rather than copy!!!

This process has got me in a tangle and I am rushing and messing up all of the stages.

Thanks for the help there, I have now got a functional PPL of Actor Framework and the Messages.🎉

I can get back to my original issue of solving my architecture haha. I am much happier that I can methodically work through the step and ideas you had for my project now that I have a separated Actor PPL.

I have started watching the NIWeek presentation from Zebra to help me get my head round the overall concept too.

I will report back if/when I get to the bottom of my architectural issues and point out and semblance of a solution for future people to stumble upon 👍.

Thanks again. I would by resigned to failure by now if you hadn't been to helpful 😁

Neil.

[NeilA]

Hi,

Thanks very much for the help, I have been making slow but positive progress re-working some of my structure and class design to remove the circular build dependencies. That is the key, with the IDE and the Class hierarchy there is no problem hierarchy work fine, it is the switch in mentality to remember to not couple the resultant PPLs in non-manageable way.

So as I have done some of the re-organisation, I am at the next point which is creating the build specs and projects, which is where my next question lies.... Do you need to make multiple versions of projects to handle PPL refs in one and raw source code or do you immediately switch to PPLs and have to re-build lower level stuff if it changes and work cyclically like that?

Cheers,

Neil.

[CaseyM]

Normally you'd switch out the source libraries for PPLs immediately and re-build if/when necessary. Using something like the MGI Solution Explorer to automate that process can help a lot.

There's also the option of the LabVIEW Solution Builder if you wanted to continue working only with source (though I haven't been able to use it much yet so YMMV).