Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7824519
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 2, 20262026-06-02T08:37:32+00:00 2026-06-02T08:37:32+00:00

While debugging i press F11 often to step into a function. For this project

  • 0

While debugging i press F11 often to step into a function. For this project i use properties everwhere which is simply a RAII wrapper that checks if i have set the variable and gives me an assert if i have not. Its been useful.

However now debugging is annoying since F11 will step into the property. Can i skip it somehow? by writing attributes, keywords or anything?

I am using VS11beta

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-02T08:37:34+00:00Added an answer on June 2, 2026 at 8:37 am

    This is quite easy to set up when you’re dealing with managed code. You can manually mark the function with the DebuggerHiddenAttribute class, and even turn on built-in debugger settings like “Step over properties and operators”.

    Unfortunately, automatically stepping over a particular function is not supported by Visual Studio for native C++ code. (At least, it wasn’t supported up until VS 2010—I haven’t had enough time to play with VS 11 to see if this is something they gave us to make up for the fact that they stole all our colors.)

    There is a workaround, though, documented a long while ago on Andy Pennell’s blog:
    How to Not Step Into Functions using the Visual C++ Debugger

    Essentially, you edit the following registry key (for VS 2010):

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0\NativeDE\StepOver
    

    or for 64-bit applications:

    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\NativeDE\StepOver
    

    to specify a regular expression that will be matched against functions by the debugger.

    For example, if you don’t want the debugger to step into overloaded operators, you can use the following expression:

    \scope:operator\oper:=NoStepInto
    

    As the disclaimer in the blog post says:

    This is not a documented feature. Well obviously you are reading this “documentation” right here, but what I mean is that is not guaranteed to work as it was never officially tested, not is it supported by Microsoft. Its existence in future versions or update to current versions is not guaranteed.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

i get this dialog while debugging code in visual studio 2008. (your step-into request
While debugging a project in MonoDevelop how can I step into Mono Framework source
I often accidently step into code that I'm not interested in while debugging in
While debugging jQuery apps that use AJAX, I often have the need to see
While debugging a WCF service I came across this issue. I use an HttpURLConnection
While debugging through a .NET 3.5 SP1 project which is contacting a local web
While debugging I found that this kind of functions: var f = function() {};
While debugging a large scale project, I use links in the log printout to
While debugging python application, I normally use pdb / ipdb's set_trace() function to programmatically
While debugging crash in a multithreaded application I finally located the problem in this

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.