Connect Debugger Without a Re-Compile/Re-Send
Started by Stuart Crawshaw, Jul 12 2011 04:27 PM
5 replies to this topic
#1
Posted 12 July 2011 - 04:27 PM
Hi all,
I was just wondering if after my project is built and the netduino is in-situ, is it possible to then reconnected the computer to the USB port and view the debug messages from the code (Debug.Print("")) without having to hit the debug button in c# Express and rebooting the netduino?
Hope this made sense...
Thanks again for all of your help on this and other topics.
Regards,
Stuart.
Intelligent People Aren't Afraid To Ask For Help.
#2
Posted 12 July 2011 - 04:39 PM
Hi Stuart,
That's possible! You can start MFDeploy.exe and press F5 to follow those texts.
"Fact that I'm a moderator doesn't make me an expert in things." Stefan, the eternal newb!
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
My .NETMF projects: .NETMF Toolbox / Gadgeteer Light / Some PCB designs
#3
Posted 13 July 2011 - 10:29 AM
Hi Stuart,
That's possible! You can start MFDeploy.exe and press F5 to follow those texts.
Awesome, Ill give that a try.
Thanks again Stefan for your help and support on my ever growing quest for netduino knowledge
Cheers,
Stuart.
Intelligent People Aren't Afraid To Ask For Help.
#4
Posted 15 October 2011 - 09:56 PM
Hi Stuart,
That's possible! You can start MFDeploy.exe and press F5 to follow those texts.
Does this mean that the netduino will still be sending bytes when it is running in a disconnected "production environment"?
The reason I ask is that I want to know if I should either remark out all Debug.Print lines or build and deploy in Release mode to prevent wasted CPU cycles when I'm not connected and debugging?
It's kind of like the light in the fridge. I have no way to check if it's really turning off after I close the door!
Thanks!
#5
Posted 16 October 2011 - 01:45 AM
Hi Darrin,
In .NET Micro Framework, Debug.Print statements are still be output to the debug port when disconnected from the PC (regardless of Debug or Release build).
You can use conditional compilation statements to stub these out. Compiling and deploying "production RTM" (no-debug) firmware may also stub the Debug.Print statements.
Chris
#6
Posted 17 October 2011 - 01:15 PM
Exactly, there is actually an issue on CodePlex for that (and probably the reason why it is Microsoft.SPOT.Debug and not System.Diagnostics.Debug).In .NET Micro Framework, Debug.Print statements are still be output to the debug port when disconnected from the PC (regardless of Debug or Release build).
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users