Before you can review your recording several things must be done.
To compile your application with RevDeBug, load your program’s solution into Visual Studio.
Next, click on the RevDeBug menu and make sure, that Use RevDeBug Compiler button is checked.
After that just Rebuild your solution.
Rebuild process shouldn’t differ from rebuilding without RevDeBug
Please note: Executables and Libraries within RevDeBug will work in a production environment
(for developers), since they are built with additional instructions, making them less efficient than
end-user products or web applications. Once these have been debugged the instructions can be removed,
making it possible to ship the code to a live environment for customers.
while rebuild is in progress we can dock the most important window of RevDeBug: Current state viewer / Control Panel. From Control panel you can display and navigate through your recording
Select RevDeBug from the top menu and dock the ‘Current state viewer / Control Panel’ tool
in one of the panels within Visual Studio.
By now it should look like this. Important detail here is that Record states should be active(green). This button indicates, whether you want to receive recording states at this moment.
Once this is in place, run the application you want to analyze. You can do it with the standard ‘Start’ command of Visual Studio or run it independently from your disk, either way;
the compilation process has already prepared it and sent all of its states directly to your IDE.
Please note some applications may function slower, running with RevDeBug depending
on the amount of processing capacity available to you.
A flashing indicator on the Record states button indicates that RevDeBug is receiving data from
You can switch this off, to stop receiving data at any time, just press the
Record states (the button turns grey).
During compilation process RevDeBug generated metadata file, that can be compared to PDB files used during debugging.
Click on the ‘Load RDB metadata…’ button, and you will be asked to locate metadata file. Go to the output directory of your project. You should find there one, or more files with .tmsx extension. choose any of them (RevDeBug will automaticly find others) and confirm your choice.
Remember, that the ‘loading RDB metadata’ step must be done only once for specific solution, so after subsequent rebuildings you don’t have to worry about it anymore.
Next time the metadata must be loaded is after reopening Visual Studio, or after changing solution 10 times, because that many paths are remembered by RevDeBug.
When the IDE part of RevDeBug receives recorded application states it doesn’t display
them at once as it could interfere with your work. To do so you need to click on ‘Show recorded
After you do so you can browse all of the recorded data, since RevDeBug makes each line of
code, function and runtime step visible inside the IDE.
The default path to generated recording is