Comments on: A Taste of Live Code Editing With Visual Studio’s Tracepoints Interesting that the feature exists explicitly. I once found out about it implicitly: I created a breakpoint with condition "x == 100", but I mistyped and it came out "x = 100". When the code ran, x immediately got set to 100 and it all broke... but I recognized the possibilities. ;) Interesting that the feature exists explicitly. I once found out about it implicitly: I created a breakpoint with condition “x == 100″, but I mistyped and it came out “x = 100″.

When the code ran, x immediately got set to 100 and it all broke… but I recognized the possibilities. ;)

]]>
By: Protector one/2011/05/19/a-taste-of-live-code-editing-with-visual-studios-tracepoints/#comment-4870 Protector one Wed, 25 May 2011 18:20:00 +0000 Shut Up Shut Up Shut Up! Visual Studios is the worstesst editer evar! People who use it are all moran noobz! Anyway...Wow, thanks for this post. I've used tracepoints instead of printf for a long time, but never knew about the curly-brace code execution option. Another tip is that there's a place in the registry where you can change the default text in the "Print a message" box, if you don't care about the thread name all the time (for example). Shut Up Shut Up Shut Up! Visual Studios is the worstesst editer evar! People who use it are all moran noobz!

Anyway…Wow, thanks for this post. I’ve used tracepoints instead of printf for a long time, but never knew about the curly-brace code execution option.

Another tip is that there’s a place in the registry where you can change the default text in the “Print a message” box, if you don’t care about the thread name all the time (for example).

]]>
By: Stefan Boberg/2011/05/19/a-taste-of-live-code-editing-with-visual-studios-tracepoints/#comment-4857 Stefan Boberg Wed, 25 May 2011 15:00:00 +0000 Sweet! News to me :) Sweet! News to me :)

]]>
By: Colin Barré-Brisebois/2011/05/19/a-taste-of-live-code-editing-with-visual-studios-tracepoints/#comment-4656 Colin Barré-Brisebois Fri, 20 May 2011 19:14:36 +0000 Even though this might be useful in some situations, I don't see how it is more useful than simply executing code in the Command Window when a regular breakpoint is hit… (E.g., "? done = true;") Equally useful perhaps, but tracepoints seem to require more effort. Even though this might be useful in some situations, I don’t see how it is more useful than simply executing code in the Command Window when a regular breakpoint is hit… (E.g., “? done = true;”)
Equally useful perhaps, but tracepoints seem to require more effort.

]]>
By: Rick Appleton/2011/05/19/a-taste-of-live-code-editing-with-visual-studios-tracepoints/#comment-4638 Rick Appleton Fri, 20 May 2011 05:56:25 +0000 Compile times are almost guaranteed to be too long no matter what if you use C++ :-( Compile times are almost guaranteed to be too long no matter what if you use C++ :-(

]]>
By: Daniel/2011/05/19/a-taste-of-live-code-editing-with-visual-studios-tracepoints/#comment-4616 Daniel Fri, 20 May 2011 01:42:45 +0000