Did you know… You can use Tracepoints to log “printf” or “console.writeline” info without editing your code? - #237

Visual Studio Links #40

Visual Studio Hacks — Sun, 22 Jun 2008 20:33:34 GMT

My latest in a series of the weekly, or more often, summary of interesting links I come across related to Visual Studio. I've been on vacation in Alaska for 10 days so this is an extra long list of links. Sara Ford: Tip of the Day #236 covers the file

Link List 20080617

Guru Stop — Tue, 17 Jun 2008 18:21:51 GMT

· Everything You Wanted To Know About MVC and MVP But Were Afraid To Ask · Functional Programming in

Trace to output window without adding code.

Peter Ritchie's MVP Blog — Fri, 13 Jun 2008 20:10:03 GMT

Want to trace some run-time data to the output window while debugging without changing and recompiling

re: Did you know… You can use Tracepoints to log “printf” or “console.writeline” info without editing your code? - #237

MarcT — Fri, 13 Jun 2008 18:58:29 GMT

Tracepoints could use a weeks of tips themselves. Stuff that's really hidden like all the special words ($FUNCTION, $CALLER, etc) - there are some that are not listed in the dialog (i.e. $TICK for timing info). Also, formatting - you can write {foo,x} to see foo in hex, for example.

My favorite secret unsupported feature of tracepoints is that the default text for a new tracepoint ($THREAD: $FUNCTION or something) can be changed via the registry.

Feature request: Save my currently active tracepoints to a file so I can load them quickly next time this same function breaks.

re: Did you know… You can use Tracepoints to log “printf” or “console.writeline” info without editing your code? - #237

Bryant — Fri, 13 Jun 2008 16:58:29 GMT

Great feature, though this debuted in VS2005, not 2008...

re: Did you know… You can use Tracepoints to log “printf” or “console.writeline” info without editing your code? - #237

Alex Black — Fri, 13 Jun 2008 16:12:16 GMT

Great tip Sara, thanks. I hadn't heard about that, I will have to try it out.

- Alex

re: Did you know… You can use Tracepoints to log “printf” or “console.writeline” info without editing your code? - #237

Serge Wautier — Fri, 13 Jun 2008 16:12:07 GMT

Thanks soooooo much for uncovering these TracePoints. I would never have found them alone! (Now, WHO uses the context menu to set a breakpoint?)

Wait, it works for Compact Framework debugging on Windows Mobile devices as well.

A very nice birthday present you came with ;-)

re: Did you know… You can use Tracepoints to log “printf” or “console.writeline” info without editing your code? - #237

John Garland — Fri, 13 Jun 2008 16:04:02 GMT

Thanks for the tip Sara. One nit, however...I am not sure this is actually a "new feature" in VS2008 - it is just more accessible in VS2008 than it was in VS2005. In VS2005, simply drop a breakpoint (F9) and then right click on the breakpoint icon in the margin or on the line where the breakpoint itself resides. From the breakpoint popup select "When Hit" and check "Print Message". If "Continue Execution" is checked (which it is by default as soon as you select "Print Message"), you have a Tracepoint.

a-foton » Did you know??? You can use Tracepoints to log ???printf??? or ???console.writeline??? info without editing your code? - #237

Fri, 13 Jun 2008 13:48:20 GMT

PingBack from http://blog.a-foton.ru/2008/06/13/did-you-know%e2%80%a6-you-can-use-tracepoints-to-log-%e2%80%9cprintf%e2%80%9d-or-%e2%80%9cconsolewriteline%e2%80%9d-info-without-editing-your-code-237/