Microsoft Code Digger

Microsoft DevLabs Free

Code Digger analyzes possible execution paths through your .NET code. The result is a table where each row shows a unique behavior of your code. The table helps you understand the behavior of the code, and it may also uncover hidden bugs. Through the new context menu item "Ge...

(57) Review
Visual Studio
2013, 2012
Download (42,531)
E-mail Twitter Digg Facebook
Add to favorites
Reviews (57)
Q and A (27)
Sign in to write a review
Sort by:

by gregorw | July 15 2015

great work - there is salvation from TDD hell

by teunvg | June 08 2015

by Marcus Holmgren | May 26 2015

Easy tool to use and find any missing test cases for your methods.

by Mr Yossu | April 15 2015

Worked as shown in the dumb sample code, but when I tried it on some real code, it didn't show any results at all. The status bar at the bottom of the Inputs/Outputs window says "Pex: finished" but nothing is shown.

Shame, it looked useful, but if it can't handle real code, it's a waste of time.

by ArranM | April 08 2015

by Robert E. Bratton | March 25 2015

by madGameMaker | March 23 2015

I really like it! Nothing more to say, I've been using it for a couple of days and it's brilliant for my small scope projects

by Reid Hochstedler | February 06 2015

by dmodiwirijo | February 04 2015

by Lakshmipathy G | January 05 2015

It is helping to a great Extend. Thanks Loved it.

by kalkie | January 03 2015

by Michael L Perry, Faceted Worlds | November 30 2014

Great for simple algorithms. But it seems to give up too early on complex ones. I've been trying to get it to "discover" the perfect bowling game by asserting that score < 300, and so far it hasn't found it.

by cainem | November 28 2014

Very, very good but where is Pex?

by MargoB1 | November 27 2014

I have found this tool very useful - generating cases I would not have thought of and obscure conditions that would potentially stop the application - I can now account for these conditions in error handling

I am very pleased as this will increase the robustness of my application - although it goes out of bounds regularly but I'm not sure if thats a problem with the code i'm testing

by Roomkey | November 27 2014

by Andrey Kurdyumov | August 26 2014

Good tool, but lack of advanced features make it hard to use on large projects, since you have to manually test each method for potential bugs.

by RDHammond | August 22 2014

by Samuel Muñoz | August 04 2014

A must!! A nice extension for testing.

by JoaoMarques- | June 24 2014

by Saravana J | June 18 2014

Awesome tool! Really promising. The UI could be much better though.

1 - 20 of 57 Items   
Sign in to start a discussion

  • Error: Monitoring of X86 code not properly enabled
    1 Posts | Last post June 01, 2015
    • starting monitored process
      listening to monitored x86 process (cold start)
      monitored process exited with monitoring of X86 code not properly enabled (-1016 - 0xfffffc08)
  • No results
    1 Posts | Last post March 15, 2015
    • Just installed this extension, and ran it on a few methods in my code. In every case, it didn't show any results at all. The status bar at the bottom of the Inputs/Outputs window says "Pex: finished" but nothing is shown.
      Don't know if it's relevant, but the title bar of the panel says "Inputs/Outputs - stopped" even though I never stopped it. I set it running and waited.
      I tried this on a couple of methods in a business logic layer, and also on ones in an MVC controller. Same (lack of) results in all cases.
      Shame, this looked like a useful tool, but it doesn't seem to do anything on real code.
  • Smart Unit Tests in Visual Studio 2015 leverages the Pex Engine
    1 Posts | Last post January 14, 2015
    • I want to take this opportunity to mention that this functionality now ships as "Smart Unit Tests" starting with the Visual Studio 2015 Preview.
      Please try it out and let us know your feedback.
      You can send us feedback using any of the following:
      (1) Using the send-a-smile feature in Visual Studio (
      (2) On our blogs on msdn (,
      (3) On twitter @pvlakshm.
      (4) Right here.
      Thank you for your continued support.
      Pratap Lakshman
  • Extract Or Copy the Results
    1 Posts | Last post January 05, 2015
    • Please enable us to Copy the Results or to Extract the code. This will help to fix the functionality.
  • Get "The extension manifest is invalid" error
    2 Posts | Last post September 09, 2014
    • Get "The extension manifest is invalid" error when install to VS2013 Professional...
    • Solved. The error was because of removed VS2010:
  • path bounds exceeded
    1 Posts | Last post June 03, 2014
    • Can anyone tell me how to avoid the 'path bounds exceeded' ?
  • StringBuilder input data options
    1 Posts | Last post January 10, 2014
    • Could you analyze StringBuilder the same as string?
      And try the same input data options.
  • Visual Studio 2013
    4 Posts | Last post December 07, 2013
    • Do you know if and when a version for Visual Studio 2013 will be released?
    • Please let know... waiting for it
    • I also would like a VS2013 version
    • We just released an update that enables Visual Studio 2013 support.
  • Support VS 2013
    2 Posts | Last post December 07, 2013
    • Could you add Visual Studio 2013 support?
    • We just released an update that enables Visual Studio 2013 support.
  • Constructors used
    2 Posts | Last post October 10, 2013
    • Hi together!
      CodeDigger is a great tool and we like to use it in production! But I think I encountered some problems. Especially with constructors. It seems, that CodeDigger does not instantiate a class by all available constructors. Sometimes it seems, that CodeDigger does not used the standard ctor as well. Is that correct?
      Further, sometimes CodeDigger does not generate any outputs! What does that mean?
      If you like I can send some code examples to show the problem with ctors or something else and I hope you can answer my question! 
      Thanks a lot in advance and best regards from Berlin!
    • I have to mention, that we use Fody for aspect-oriented programming. When I weave the NullGuard into the project, every output from CodeDigger disappears.
      But the question about the ctors is still valid! :)
      Thanks a lot!
1 - 10 of 27 Items