That's why I said not 100% sure. I am 100% sure it was a command line argument to devenv, just not 100% which one. But yeah, I did spend 4-5 hours on it.

Note that I believe that requires Admin elevation, which may not happen during your install?  But I also had your templates after your(and MF) install, they just disappeared later. From what I've read, this latest addition of 'portable library' stuff has created many new issues (hard coded links to v2.05 of System.Core), of which I am guessing this is just 1 more.

I fought missing mf templates for a day recently. They were there in the proper directories, but never showed up in Visual Studio.

I uninstalled / re-installed 3-4 times, nothing changed.

I think this article finally made things work again; 

http://chiragrdarji....lled-templates/

I'm not 100% sure it was that, but it was some command line argument to devenv. Apparently VS still has some issues finding templates occasionally.

Thanks Jack.  The mac has been configured, that is why I indicated it had gotten a valid dhcp IP - it pings fine, but it is nmikaweb server that is getting the network down exception.  I'm trying other IP stuff to see if I can figure it out. One thing I notice consistently is the use of non-dhcp, which might be a hint, I can explore that angle on my own more.*

Yes, debugging is crucial, otherwise I'd just as soon use an arduino. So I need to do both, communicate and debug. I would have to disagree though on simplest way to communicate, if I can code a object, import its wsdl file into visual studio, and treat a object on a remote device (netduino) as local (intel NUC), that is simple.  I understand your description is more from a bytes across the wire point of view, not a developers point of view.

I'll take a look at the internet of things.

*so yeah - after double checking before posting this, I am finding totally unreliable unrepeatable dhcp usage. time to go fixed.

Update: yep, going to fixed, it is now communicating.  So a question remains, has anyone used dpws and what was the experience, good or bad?

Hello all, Netduino Noob here, so apologies. I'm quite experienced as a .Net developer, but slightly new at robotics and MF, having done a little of both.

I have a robotics project where the Netduino is intended to serve as the hardware interface, and communicate back up to the WIndows app.

This involves some sort of remoting. So in googling, I've run across a stale remote project (http://kaushikspotse...s.codeplex.com/), Microsoft dpws, and now this.  

I tend to gravitate towards this since it has some fairly recent activity and is the most specific for the Netduino.  Is that the correct assumption?

I also notice that at present because of interaction with the debugger a separate FTDI is needed. I happened to have the Sparkfun 3.3v FTDI breakout board already (not the cable, but the equivalent board).  Will this get me going? Am I on the right path?

Mike

I do not really want internet access. I am just trying to develop a robot platform above a line following LED blinker.  You know, collision avoidance, drive motor encoders, IMU, LIDAR, ICP-SLAM, basic robotics stuff  :|  Then move on to arms and IK, motion planning, high school stuff.

So an Intel NUC main processor w/windows 8 (and vs 2013), a netduino for I/O.  I guess I must be bleeding edge or something. I am not finding anything similar. Sigh, I'll work through it eventually.

http://www.spiked3.com/?p=338

Any speed comparison between dpws(ethernet) and USB? I can find out the hardware differences (12mbit v 10mbit), but some feel for the actual stack throughput / latency on this particular device (plus 2) would be helpful. right off the bat I would think dpws would have the advantage of ease of use (WSDL) in visual studio, if it performs as well, does not require extra hardware, then it is the obvious choice. This assumes dpws works as intended (and any insight on that would be helpful).

So far I have been unable to get any ethernet communications going. MF deploy indicates good DHCP obtained config, but ReceiveFrom throws 'Network is down'.

Again, thanks for the noob pointers. Yes I am quite experienced as a developer, Remoting, WCF, WPF all all pretty much second nature to me and I cringe on the thought of not having them.  But Solder? I cringe at thought as well  But as I mentioned, I have done some. I have the saleae analyser that does I2C and others, as well as the newer one which adds analog (oscope), on order  

Yes getting vs2013 up was the first step.

So I had a look at the internet of things. I ran step 1 ok, step 2 was not blinking the light, so I added a Parameters.Setup(), because I didn't see where the proper pin was being set.  And that invoked the 'sign up for you private key, we only want your personal information' routine and I bailed.  I'll see what I can get from the code, but I really dislike that kind of dishonest thing. If it truly can be run without it (as advertised), one preprocessor variable should do the trick, not 30 minutes of chasing down unrelated code.

I'll take a look at Mark's blog now.  Mine is at http://www.spiked3.com  <- warning; not open source friendly at all

actually looks like you need to comment all 4

The amazon one is supposedly gen 1. I read somewhere that WIndows required gen 2 BUT I was told that was not the case, and that is confirmed here; 

http://ms-iot.github...ghtAGalileo.htm

So that Amazon buy should be good.

So that would be a problem for Windows and Linux then? As in a hardware limitation?

I'm really starting to get the impression none of these devices are going to satisfy the needs from a hardware standpoint. If you want to play in the IoT space you better have a SMC soldering pencil ready (metaphorically).

After a week of trying to make it work, I'm going to the FPGA board now.

I am disappointed in all of them at the moment.

How long have we been hearing of new MF support coming real soon?

Either people can not estimate things, or they intentionally underestimate. In either case these are the same management teams doing the work, so I have to assume their product is as solid as their estimates, or best case as over sold.

Or is there intentional under funding? 

Either way, it does anything but inspire confidence.

 The Netduino is as stable as a rock and compared to the Intel, light years ahead. ...

What is your experiences that reveal that? Unless it is that it has been 4 years without enhancements and bug fixes, I get that.

I've only played with the IoT a minute, but the debugging on it was rock solid, as opposed to a random number of reboots on the netduino every time I hit run.

As far as non-debug running, the IoT is months old, versus years for the Netduino (and MF) family. Not quite a fair comparison.

https://webchat.free...indowsondevices

If shipping to the US is included, put me down for 50. I'll hand them out at robot meetups

Oh wait thats just the chip, n/m.

Pete,

What I was refering to was this blog posts; http://blogs.msdn.co...6/27/hello.aspx

The post clearly states "in the next few weeks", and was posted in June. I'm sure that was true from the bloggers perspective, but given a lack of anything else, it is also what I made decisions with.

I think many here have expressed the frustration with being left to believe something is coming soon, then hear nothing more about it for a year or more.

Best of luck to you, I truly hope for your success, I have a lot invested in it at the moment. I'm really hoping that was not a bad decision. 

I have not received one, although I did eventually get an email suggesting I would.  I followed their IRC chat for a few days and it was very quiet.

Ms was also supposedly at nearby at a coffee shop (in Seattle) with boards, but when I attempted to drive there, I could not find parking (and I am handicapped) so I came back home.

I believe the intention is to provide firmware that will allow non ms-versions to run the MS dev kits. But that will be sometime AFTER initial release of MS dev kit versions.

You guys do realize 'windows on devices' was the old marching orders? The new orders are different (although confusion seems to be a recurring theme at MS) ....  layoffs are coming this week - it will be interesting to see where and how deep.

Chris I was referring to the combobox choice when you signed up for information.  Instead of a check box, like the (incomplete) 'which dev boards have you used?' section, they ask what experience do you have, pick one; Win32 or WinRT. Anyone even vaguely technical would know there should be a lot more choices, and not exclusive.

No instead, they handed the web site off to some 'designers', and never followed up on what was produced. And like I said, even if you fill out the form and request more information, you never hear anything, from anybody.

I used to work at Microsoft, I left around the time this sort of 'management' started to become the norm. I truly feel sorry for the technically competent people at Microsoft. I hope the MF team can make something happen anyhow, but looking at their track record the last few years - I wouldn't invest much.

edit: I see they changed it in the last 12 hours. Hmmmm.

Look at their web site (https://www.windowsondevices.com/). They claim a person can not have used both Win32 and WinRT for development. Of course that is not true, it is an artifact of web designers that have no clue, but I suspect it continues to represent leadership at Microsoft, non existent.

I filled out that form months ago, nothing. What a way to run a company.

Which makes it even more confusing as to why its not here, front and center, but I think that was already mentioned. All I know is the new boss is saying 'we aren't doing what we were doing, but I can't quite tell you what we are doing now'  - I live here, I get the inside noise a lot.  Maybe it will become clearer in a few days.

And of course if it isn't happening here (I assume MF is not, having not met a single person yet that works on it) it takes a while to trickle down anyhow.

heh, re: born for IoT, you can fool these youngins, but be careful with us old iron types. We know what it was and why

Oh man, the web site redirects now.  The suspense is killing me.

 

I'd yield a bit of faith to MS. Better, to some people "believing" in a concrete direction...

 

Seriously? With their track record over the last 5 years? Windows 8 (which I understand was tough nut to crack, but they didn't do so well), Windows phone (oh the stories I could tell you from that dev department), CEOs, firings (leaving the root problems in place)?  

You have faith?  You are a kind man  I am a Ms fanboy for life, but it is mostly because I'm too old to learn anything new

I did not intend to imply people were parked in handicap spots, just the opposite. Seattle is a very handicap unfriendly city. Most of the people are (on average) young wealthy health nuts so not much attention is given to/for handicap. Thus there is NO handicap designated parking. 

The more I think about it, the more I think I probably would not be a good candidate for one of these boards anyhow. I don't get it. I have yet to understand ANY reason for it to exist, and especially no reason to take attention away from other existing platforms. It really looks like another Ms throw money at the wall, and see if anything sticks, and I can tell you the outcome.

The chat today on IRC was that indeed Ms is 'selecting' who they will be sending kits to, based on intent.

The internet is full of comments, I miss some.

One email I got said they would send me a device soon.  Another comment says all devices have been sent. No one here has indicated they received devices.  I saw nothing in (limited) reading for non-disclosure about not saying you have one. Maybe I missed that as well.

The more I look at it I'm not really sure what I would use this for.  Does anyone understand why a device would boot windows then provide an exact emulation of an arduino (using wiring as the language and NO ui?).  I've got to assume something different is in the pipeline, and this is just a stepping stone. Either that or MS truly has lost its marbles. So at this point, I trust Chris's idea that great things are happening with MF, at least that WAS the intention.  Today the knife falls and we will see where and on who.

I want that Galileo board! Submitted my application by have not been selected. Oh well, I will keep playing with my Netduino / Arduino for now. 

Suggested course of action. Come up with a specific cool idea to use it for.  

Join the IRC channel and talk about it, You might get noticed <wink wink>