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...

(40) Review
Visual Studio
2013, 2012
Download (30,860)
12/7/2013
0.95.4
View
E-mail Twitter del.icio.us Digg Facebook
Add to favorites
Description
Reviews (40)
Q and A (22)
Sign in to write a review
Sort by:

by JoaoMarques- | June 24 2014

by Saravana J | June 18 2014

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

by Christiaan Rakowski | June 12 2014

by MargoB1 | June 03 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

by Rolf Huisman | April 29 2014

by GBotros | April 16 2014

by Chen Rudai | March 27 2014

very very useful and helpful.

by CoolHacker | March 10 2014

Very good! But I miss so much full functionality of PEX in VS2012

by faenocasul | February 17 2014

Nice tool to quickly check for potential bugs. Not quite as throrough as good unit tests, but faster.

by Shaiju Janardhanan | January 21 2014

Trying to run on Visual studio 2012 Professional throws the following exception "Microsoft Pex Exploration Host has stopped working".
On selecting "Generate Input/Outputs table" produces the input/output table followed by this exception

by Sonicflare_ | November 16 2013

Very easy to use and quickly see the potential input sanitation problems!

by Realapisby | November 10 2013

What an awesome tool.. Help us to explore our logic by providing accurate input parameter for each logic branch.. You should try this as one of your ultimate tool :) It really saves a lot of our time to explore every logic branch in our apps..

by Robin Sedlaczek | October 08 2013

Great tool to generate unit tests for parameter boundary tests. I like toi see it integrated into Visual Studio and the testing features as far as in ReSharper! :)

by larrym996i86 | October 06 2013

I like the minimalistic approach as compared to the old Pex.
Adding cut and paste from the inputs/outputs window would be great.
Showing code coverage in the target code would also be good.

I got burned with Pex and Moles when there was no replacement/upgrade/fix for VS2012.
I told people: "Let the name of Pex and Moles be stricken from every book and tablet, stricken from all pylons and obelisks, stricken from every line of code". :(
http://www.imdb.com/title/tt0049833/quotes
Maybe this could be open sourced so it won't die when Nikolai and Peli move on to something else.

by sigol | September 09 2013

O M G
What a fantastic tool. Whilst it's not bullet proof, it shows amazing promise.

I ran the Code Digger over a number of real-world methods and it immediately identified dozens of edge cases we hadn't thought of.

This is getting rolled-out to my team TODAY!

Well done. Brilliant. Really brilliant.

by Nerdling | September 05 2013

by sm_developer3 | September 02 2013

Doesn't work.

starting monitored process
listening to monitored x86 process (cold start)
monitored process exited with exit code -532462766 - 0xe0434352

by Clayton C. Peddy | August 26 2013

by vpalle | August 19 2013

Please make it possible to copy from the inputs / outputs table.

by Angel L. Castro | August 09 2013

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


  • 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!
      Robin
      
    • 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!
      
      Robin
      
  • Crashed
    2 Posts | Last post September 02, 2013
    • Faulting application name: Microsoft.Pex.x86.exe, version: 1.0.0.0, time stamp: 0x51df1ba3
      Faulting module name: KERNELBASE.dll, version: 6.1.7601.18015, time stamp: 0x50b83c8a
      Exception code: 0xe0434352
      Fault offset: 0x0000c41f
      Faulting process id: 0x1e4c
      Faulting application start time: 0x01cea7e90cb4b47c
      Faulting application path: C:\Users\EPDev1\AppData\Local\Microsoft\VisualStudio\11.0\Extensions\b1k1evud.1o3\Microsoft.Pex.x86.exe
      Faulting module path: C:\Windows\syswow64\KERNELBASE.dll
      Report Id: 4cacada5-13dc-11e3-9407-2016d89bd407
    • Application: Microsoft.Pex.x86.exe
      Framework Version: v4.0.30319
      Description: The process was terminated due to an unhandled exception.
      Exception Info: System.InvalidOperationException
      Stack:
      
      Server stack trace: 
         at Microsoft.ExtendedReflection.Remote.RemoteServer.GetClient(String clientID)
  • Pex general setting in Options
    2 Posts | Last post August 19, 2013
    • Hi
      
      Does Code Digger look at the Pex/General settings in visual studio options?
      E.g. can I set a different MaxBranches value.
      
      Thank you.
    • After further investigation I can conclude it does..
  • Error while running
    2 Posts | Last post August 04, 2013
    • Hi,
      I have tried to use it on PLC, VS 2012 Update 3 and W2K12 Standard and I get following info in Pex output:
      listening to monitored x86 process (cold start)
      monitored process exited with monitoring of X86 code not properly enabled (-1016 - 0xfffffc08)
      
      On W2K7 and VS 2012 Update 3 same code works.
      
      Any idea how to make it working?
    • Haven't used pex before but is there a way in code digger to generate unit test code output?
  • How to know where error occured.
    1 Posts | Last post July 31, 2013
    • Hi,
      First of all thanks for this plugin I really appreciate your work here.
      Could you please guide me how to know at which line/method error actually occurred just like the web version of PEX (PEX4Fun) where after the output is generated clicking/selecting an error gives the error details below.
  • app.config
    3 Posts | Last post July 26, 2013
    • Code digger seems to have issues with app.config files. In several cases where it din't generate any input/output I removed app.config from the project, which resulted in input/output being generated..
    • Thank you for your feedback. We just pushed out an update that should fix the app.config file problem.
    • Yes, that fixed that one problem with the app.config. Code Digger gets a bit further now, it starts to generate the input/output table items, but once the first item is displayed on the table, Code Digger crashes and burns once again and I get the prompt to send Crash Information to Microsoft. I proceed to send the information and then rinse and repeat and watch it crash and burn again. It doesn't seem to matter the location I generate the ins/outs from (any method), it crashes everywhere in the same way. I hope that you guys are able to see the Microsoft Crash reports about this, I wish I had more time to QA this but it is still unstable so I can't use it in a real world scenario just yet.
      
      Thanks and please keep rolling out the updates.
1 - 10 of 22 Items