After you have installed the Code Digger extension, create a “Portable Class Library” project.
Write some public code, right-click on it, and select “Generate Inputs / Outputs Table”.
Wait a moment, and you will see a table, listing interesting parameter values which cover all the corner cases in your code.
If you are ready to run Code Digger on code that doesn't sit in Portable Class Libraries, then you can go to [Tools - Options...], select [Pex, General] and under [Code Digger] set [DisableCodeDiggerPortableClassLibraryRestriction] to True. Remember that even though you can launch Code Digger on almost any .NET code afterwards, Code Digger may still not be able to follow calls that leave the assembly under test. This option was introduced in the Code Digger 0.95.2 update.
Starting with the Code Digger 0.95.3 update, you can also enable the option [EnableCodeDiggerFakesSupport] that you can see in the dialog above. When both options are set to True, you may be able to run code digger on test code that uses Fakes, as shown in the following screenshot. We are looking for your feedback about this feature preview. Please send bug reports or any other feedback to the Pex team at Microsoft Research.
Try the Pex engine of Code Digger online
If you are not yet convinced that you should install the Code Digger extension, try the Pex engine in your browser on Pex4Fun.com.