Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. Visual Studio
  4. VS 2010 - Cannot debug/step into private accessor during unit testing

VS 2010 - Cannot debug/step into private accessor during unit testing

Scheduled Pinned Locked Moved Visual Studio
visual-studiodebuggingcsharptestingbeta-testing
2 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • P Offline
    P Offline
    puromtec1
    wrote on last edited by
    #1

    Can we no longer step into private accessor methods in Visual Studio 2010 during unit testing? The debugger just skips over the method instead of stepping into the private method via MyClass_Accessor class. I understand there are some issues with private methods in vs 2010's test framework, but is this problem I am having actually one of the issues? Thanks in advance.

    P 1 Reply Last reply
    0
    • P puromtec1

      Can we no longer step into private accessor methods in Visual Studio 2010 during unit testing? The debugger just skips over the method instead of stepping into the private method via MyClass_Accessor class. I understand there are some issues with private methods in vs 2010's test framework, but is this problem I am having actually one of the issues? Thanks in advance.

      P Offline
      P Offline
      puromtec1
      wrote on last edited by
      #2

      Oddly enough, it began working. [edit: Now it stopped working. After adding a unti test, I can no longer step into the source code from the accessor object]. Very annoying. [FINAL Edit: solved] I came across a similar issue here: https://connect.microsoft.com/VisualStudio/feedback/details/556756[^] Way down at the bottom of the comments: 5/11/2010 at 7:24 AM ..solution: "add a breakpoint to the code." Works everytime now.

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups