Whilst using RevDeBug only on your machine is useful, the true potential is in distributing application compiled with RevDeBug to your testers or clients. In case of an error, you will not have to try to replicate their bug in your environment - you will receive exact recording of this problem.
If your build server have Visual Studio installed, this step is easy - just install RevDeBug from revdebug-installer.exe
Otherwise you need to copy RDB compiler from a machine, where RevDeBug is already installed to build machine.
You can find RevDeBug Compiler through RevDeBug Menu (RevDeBug > Advanced > Open RevDeBug Compiler Folder).
Copy the whole folder to any place on your build machine.
Now you should copy RevDeBug.ImportAfter.targets from
to your build server in
[C:\Program Files (x86)\MSBuild\YourMsBuildVersion\Microsoft.Common.Targets\ImportAfter]
Second, open .csproj file of the project that you want to build with RevDeBug and add following MsBuild property group that will modify build process.
<PropertyGroup> <RevDeBugActive>true</RevDeBugActive> <UseRevDeBugOnThisProject>true</UseRevDeBugOnThisProject> <RevDeBugStateStorageType>Binary</RevDeBugStateStorageType> <RevDeBugCompilerPath>Your\RevDeBugCompiler\Path\</RevDeBugCompilerPath> </PropertyGroup>
Optional property, that you can add is RevDeBugStatesFileDestinationPath. With this you can specify where your recording will be saved.
Remember however, that user running application should have permissions to that path.
You must set that property and change default path, if your app is running on IIS, since any changes in website directory will reset its Application pool.
To turn off building with RevDeBug you can remove added properties, or just set RevDeBugActive to false.
If you have recording that you want to send to someone, he will need three things.
Since recording application all the time may be space consuming, you can decide when application states should be written to disk.
To turn off recording go to your application directory and open RevDeBug.setup file. First line should be
Change it to
and restart your application. Now RevDeBug won’t record anything.
If you want RevDeBug to start recording again - just revert your change in setup file and restart application.
Additionally you can use the RevDeBug Remote Rec batch scripts. They are automatically added to your application output directory:
Those scripts will modify the RevDeBug.setup file, so you still must restart your application to apply changes.
Go to the next chapter, to learn how to activate RevDeBug.