[Edmund Harfmann]

I agree that C# is the language of choice for services. (Look at the samples.) I think that VPL will be the 'language of choice' for higher level code.

C# provides the 'fast code' of the service and therefore makes sense to use at the service level. (Is C/C++ better? Yes, but the margin is not big enough any more to fuss about.) The downside of this is that for the higher level, you get lost in the details.

VPL provides the string-together ability that simplifies development (just like EasyC). You don't have to think about posting to ports. You don't have to think about what the interface is. .... It lets you concentrate on the higher level. That's also its downfall. You cannot describe trivial operations without having a service to do the work. (Why is there a math service? So that VPL can do math?!?!?)

I've been trying to build a Mars Rover in C# and it has been a pain. I'm about to scrap it and try again in VPL. It makes sense. (Now if I only had time to get back to it.) I've been getting lost in the details at this high level. I need to backup and try again with the right language. I’ve delayed using VPL since the 1.0 version for my machine crashed a lot. It was too frustrating. Maybe the 1.5 version is more stable.

There are a ton of details to get lost in at the high level. Using the environment properly requires that you know when to break tasks into smaller tasks so that the work can be split by CCR to the appropriate threads. (Big tasks = bad idea) Am I an expert? No, but I've glimpsed the power of the environment. Am I a Microsoft advocate? No, I just like a paycheck. I’ve tilted at too many windmills.

I REALLY hope that IFI will have a Bluetooth/Zigbee/whatever released addition to make this easier. (I personally would prefer a Zigbee device. Lots of range. :>)

Ed