Thanks Erel, I still am feeling like a bit of a newb ... these seem like silly mistakes, so thank you for your patience and assistance. It's very much appreciated - I promise to start few rippers in the net few posts...
OK - so now I'm trying to look at how to refactor my design a bit.
I have a class that I'd like to be populating on start-up, and then refer to throughout the app lifetime.
What seems to be the best approach (for asynchronous objects - populated by web service) is:
- in Main, start the service,
- which initiates the class, and
- then expose the class object off the service?
- so rather than main.<<class instance>>, instead
- use <<service name>>.<<class instance>>
This is now working a treat, although the emulator provides a few interesting responses to 'standard' calls...