Problem Debugging App

This morning I remembered that I had my Netduino Go stored in my filing cabinet and decided to start messing around with it again.  I brought it to work with me and updated the firmware to 4.2.2.1.  I went to update the shield base firmware as well but I was having trouble connecting to the device.  I resolved that issue (had to do with the new name of the device).  In visual studio 2010 it would try to deploy but would fail to connect to the debugger after rebooting the device.  I removed the .net mf 4.2 and installed 4.3 as well as the sdk for 4.3.  I created a new application in VS 2012 which builds just fine, it finds the device, installs, then on restart again fails to connect to the debugger.  

 

Micro Framework Device Deployment Output:

 

 

Hi Russell, Let's simplify this a bit and see if we can diagnose the connection first--and then slowly in add your application logic. Try creating a new Netduino Go Application. In that application, add one simple line of code:

Debug.Print("hello world!");

Now try deploying that to your Netduino Go. Make sure that all GoBus modules and any other accessories are detached from your board first. Does that app deploy? Does it run? Please note that VS2012 support is currently in beta. We're using it almost exclusively here...but it does have a few hiccups from time to time. Chris

Thanks for the prompt reply.  Did exactly as you asked, visual studio hangs at Waiting for device to initialize for a bit, the program never runs.  I do not have any modules connected to the netduino go at all, no extra dll's added.  Eventually visual studio reports:

 

 

Hi Russell, Okay, in this case I'd recommend moving back to the regular 4.2 SDK (NETMF 4.2 QFE2). Either way, we can create a work request for Microsoft for Visual Studio/NETMF to get this fixed in 4.3. The only time I've seen this kind of behavior is when there's a USB filter driver (or USB sniffer software) installed on a PC. It really sounds like Visual Studio is just getting detached from the USB stream. Chris

I actually started out on the 4.2 sdk initially.  I was seeing the same problem so I updated to 4.3 to see if visual studio 2012 handled it a little better.  Now I'm wondering if its the USB cable I'm using.  I do mobile development and have had issues debugging apps on my samsung phone using anything but a Samsung cable.  I was using my samsung cable with the netduino, I'm going to try this evening to see if a different usb cable produces different results.  I am not sure if this matters or not though.  As far as a USB filter driver or sniffer, I don't know anything about that.  It could be possible with the Android sdk to install that kind of driver?