I am building a aquarium controller and I would like to accomplish the following:
1. Create a Windows Application to interface with the netduino. This is my first priority.
2. Build a website which can publish my aquarium data over the web, but I will publish the data so i can get the values any time of the day.
I would like to implement one solution to cover both Web and Local applications.
Short term goal will be Temperature and my long term goal includes LED Lights, Power control (On / Off) and PH sensor.
Thanks for any suggestions.
I am working on the same project (you can see my project in general discussion) on the N+2 and I chose to implement a webserver that served up XML and took in commands. I then used an intermediate webserver (www.reefin.net) to read the XML and parse it. The controller stats on reefin.net are pulled in real time from my N+2. The webserver can (and will in my case) be extended to offer control over the controller as well. I'll be writing a windows application to monitor and control it as well (and releasing source, of course) so you can follow along as you take off on your own project. I looked at WCF, DPWS, and a few other options.
Why did I end up with a webserver on the N+2 when I specifically started out looking to NOT have one?
This one is very light weight, I didn't go with Neon's because I didn't need everything they've built into that.
I'm not bothering with rendering pages, just XML that is parsed by other devices.
It easily enables two way communication just by sending a request to the webserver.
Enables me to grab stats from another webserver and do all my logging and what not off the N+2
Hope that helps!