Two things have changed with the NoStepInto feature of the native C++ debugger in VS2010 compared to VS2008 (for a general intro see
here):
- You don't have to put your rules in HKLM anymore: you might as well put them in HKCU (more precise in HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0_Config\NativeDE\StepOver), which is of course much better
- If you put =NoStepInto things will no longer work: just leave it off.
Some examples (as entered in RegEdit)
- Name:10, Value: boost\:\:shared_ptr.*
- Name:20, Value: std\:\:.*
Happy programming!
Thanks!
ReplyDeleteHelped a log. Thanks!
ReplyDeleteFollowing this handy hint, we’d use:
ReplyDelete1) HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\10.0_Config\NativeDE\StepOver
To add the value:
10 = boost\:\:shared_ptr.*
That works great for not stepping into dull/boost code.
But only for a while! :-(
Re-opening VS2010 seems to lose that value. For me and a coleauge at least.
From what i can tell, if we actually put the values here:
2) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\NativeDE\StepOver
that unhelpful absent-mindedness will stop.
VS copies over all the values 1) -> 2) at start-up.