|Dotfuscator > Understanding Instrumentation with Dotfuscator|
In addition to obfuscation, Dotfuscator also provides features that inject code into an application. Some of that code is used to enhance the protection provided by obfuscation (i.e. Tamper Notification and Shelf Life), but Dotfuscator can also inject code that sends messages back to you about how the application is used in production. This powerful capability lets you deeply understand your application usage, which can help you make better decisions about your software priorities.
This injected code is called Instrumentation, and is most-often used with one of the PreEmptive Analytics products.
PreEmptive Analytics Workbench accepts, processes, transforms, and aggregates analytics messages for display in a web browser. It is highly configurable and customizable so that it can provide role-based, real-time visibility into application usage, adoption, user behavior and software quality - saving you time and money.
To learn more, please read about PreEmptive Analytics Workbench on our website.
PreEmptive Analytics for Team Foundation Server aggregates and analyzes exceptions and automatically creates Visual Studio / TFS work items based entirely upon rules and operational thresholds that you define. PreEmptive Analytics for TFS is designed specifically to help streamline feedback driven development, improve software quality and user experience, and increase development efficiency.
PreEmptive Analytics for TFS uses exception instrumentation. It does not require feature, platform, performance, etc. instrumentation.
To learn more, please read about PreEmptive Analytics for TFS on our website.
Dotfuscator can inject Instrumentation code for all .NET assemblies except for the following: