Didn't find answer to your problem? Contact us at email@example.com
RevDeBug comes with extendible exclusion rules that allow developers to choose what not to record. By default, RevDeBug doesn’t record variables with passwords, card numbers, and secret keys, but devs can easily extend those rules. Summarizing: RevDeBug doesn’t have to scramble sensitive data or so, because it is not recorded at all.
Data is accessible only by developers, that were granted access to the Record Server. The Record Server is an application that manages to record and deploy it on your own premises. In other words, it is as save as you keep it.
The recordings are stored on your dedicated Recording Server. Only people within your own organization and with granted access can reach them.
RevDeBug collects only the usage statistics (ex. What feature have you used, what version of Visual Studio you’re using...). It helps us improving our tool and making it more user-friendly. You can opt-out from sending the analytics information at any time by going into Tools > Options > RevDeBug > General > Send Usage Statistic.
Unfortunately, there was not much interest in .NET 2.0 support from our users, therefore, we have decided to focus on other areas of development.
If you need support for .NET 2.0, feel free to contact us at firstname.lastname@example.org.
Yes, RevDeBug support .NET framework 4.0 or later and .NET Core 2.0 or later.
Yes, it does. RevDeBug supports .NET framework 4.0 or later and .NET Core 2.0 or later.
Yes, it does. We are proud to say that you can use RevDeBug with your Xamarin applications.
RevDeBug supports .NET projects written in C# and VB.NET. Stay tuned, as there are more languages and platforms to come!
Yes, we do, and you don’t even need to reconfigure IIS to make it work both locally inside Visual Studio and remotely. Just compile your project with RevDeBug and that’s it. The next time you access your web app it will stream the recording to the Recording Server and then into your Visual Studio (you don’t even have to hit the ‘run’ button).
In general RevDeBug works very well with Resharper. The only exception is Incredi Build as our compilator does not integrate with their build. Stay tuned for future updates that may tackle this challenge.
We are capturing exceptions with their messages and stack traces, variable values that lead to the exception and code specific events like method enters or exits.
Yes. You don’t need an active RevDeBug subscription to run your application that was compiled with the use of RevDeBug.
RevDeBug does not support this feature right now, only values read or set are being recorded. With full complex types being recorded, the recording tended to get overwhelmingly large. We will certainly add this functionality in the future - once we make sure, that it will work perfectly for everybody.
RevDeBug does not inspect everything the Virtual Machine is processing, but only parts that were instrumented beforehand. Which allows fine-tuning of what you record and what slowdown you can expect.
There are two main recording modes - Crash Recorder and Live Recorder.
Below are results of running unit testing suites of various Open Source projects to give you overall feel about performance penalty:
Please refer to Requirements page.
Please refer to "Limitations" and "Known issues" sections on Requirements page
Are you looking for information on what makes RevDeBug different from other debugging tools? Check this article.
You may also be interested in the RevDeBug - IntelliTrace comparison table.
RevDeBug temporarily disables the Code Pattern Analysis, when used to build the solution. Unfortunately, we don’t play very well with it yet. If you rebuild your solution without the use of our compiler the Code Pattern Analysis should be re-enabled.
Please refer to Return policy.
Last Edited on 2019-01-10