SmartAssembly - 6.7
Viewing feature usage reports - SmartAssembly
This topic explains how to view feature usage reports submitted by your end users. To receive feature usage reports, you must first add feature reporting code to your application, and then enable it in the SmartAssembly project. For more information on setting up feature usage reporting, see Setting up feature usage reporting.
When a feature usage report is received by the web service, a counter increments showing that the feature has been used. You use SmartAssembly to view the usage counters and to export the data to a spreadsheet.
Note that viewing and exporting the counter data does not reset the counters.
To view the feature usage counters, on the menu bar, click View Feature Usage. The latest counter data is downloaded automatically.
To update the counters while viewing them, click Refresh.

Filtering reports by project and build
If you have built multiple projects with SmartAssembly but you only want to see the feature usage reports for one of them, select it from the Filter by project menu. Reports relating to other projects are hidden. To view reports for all projects, on the Filter by project menu select (All projects).
To filter reports by a build, use the Filter by project menu to select the project, and then select the build on the Filter by build menu. To view reports for all builds, on the Filter by build menu select (Show reports for all builds).

Exporting feature usage data
To export the feature usage data as a CSV file, click Export Spreadsheet.

The CSV export provides more detail than the counters alone. The following fields are provided:
User ID |
A GUID based on the Windows user SID of the user who ran your application. |
Session ID |
A GUID that is unique each time your application is run. |
Session Date |
The time when your application was run on the end user's computer. |
Feature Name |
The string passed to |
Usage Count |
The number of times the feature was used during that user's session. |
As a simple example, imagine that:
- User 1 ran your software on computer X at 12:34pm on 23 January 2011. During that session, the user used Feature A, Feature B, and Feature C.
- At 12:58pm on the same date, User 2 ran your software on computer Y. During that session, the user used Feature B, Feature C (twice), and Feature D.
- Later that day, at 3:45pm, the first user loaded your software on computer X again, and then used Feature A ten times and also Feature D.
If you click Refresh after User 1 has closed the application, and then you click Export Spreadsheet, the exported CSV file would look something like this:
User ID |
Session ID |
Session Date |
Feature Name |
Usage Count |
1 (GUID) |
GUID |
1/23/2011 12:34:00 PM |
Feature A |
1 |
1 (GUID) |
GUID |
1/23/2011 12:34:00 PM |
Feature B |
1 |
1 (GUID) |
GUID |
1/23/2011 12:34:00 PM |
Feature C |
1 |
2 (GUID) |
GUID |
1/23/2011 12:58:00 PM |
Feature B |
1 |
2 (GUID) |
GUID |
1/23/2011 12:58:00 PM |
Feature C |
2 |
2 (GUID) |
GUID |
1/23/2011 12:58:00 PM |
Feature D |
1 |
1 (GUID) |
GUID |
1/23/2011 3:45:00 PM |
Feature A |
10 |
1 (GUID) |
GUID |
1/23/2011 3:45:00 PM |
Feature D |
1 |
For more detailed analysis, see Feature usage reporting analysis spreadsheet.
Was this article helpful?
SmartAssembly
- Using Smartassembly to obfuscate a windows service
- Obfuscation not renaming identically-named methods in different classes
- Serialization exceptions occurring in obfuscated assemblies
- SmartAssembly skipping obfuscation of some classes in your assembly
- SmartAssembly is not merging or embedding all assembly dependencies
- Can I customize the path to the MDB database?
- System.InvalidOperationException when attempting to connect to local SmartAssembly database
- Protecting website code using SmartAssembly
- Visual Studio Deployment Projects including unprotected builds
- SmartAssembly MSBUILD tasks failing because of difference in log4net assembly
- SmartAssembly Error Reporting: This application has submitted too many reports
- The assembly is being merged, but the dependent assembly isn't
- ERR 2002: Server did not recognize the value of HTTP Header SOAPAction
- The error report is not associated with a valid project ID - SmartAssembly
- Application built with an evaluation edition of SmartAssembly
- How end users can change their participation in Feature Usage Reporting
- Log file for SmartAssembly
- Moving SmartAssembly to another computer
- 'Using JET databases is not possible in 64-bit applications' error when using MSBuild or TFS
- SmartAssembly stack trace is invalid when Method Parent Obfuscation is enabled
- Upgrading SmartAssembly version 4.x to version 5
- Upgrading SmartAssembly Standard to Professional
- Problems building WPF applications with SmartAssembly 6.7
all products
- Some Red Gate products identified as containing a trojan by Anti-Virus software
- Activation may fail with Unknown Error -1
- Product uses web help although a CHM file is available locally
- Argument exception resulting from missing environment variable
- Check for updates may fail when used through proxies
- 'Unidentified Publisher' error when repairing or uninstalling
- Licensing activates product as standard edition
- Moving Red Gate software products to another machine
- Red Gate tools log locations
- The application UI opening slowly when there is no internet access
SmartAssembly
all products
- Red Gate product acknowledgements
- Activating your products
- Activating your products
- Red Gate bundle history
- Check for updates
- Troubleshooting Check for Updates errors
- Current versions
- Deactivating your products
- Installing Red Gate products from the .msi file
- Requesting additional activations
- Serial numbers for bundles
- Reactivating using a different serial number
- Extending your trial
- Finding your serial numbers
- Moving a serial number from one computer to another
- No response received for manual activation
- Licensing and activation resources
- Licensing and activation resources
- Troubleshooting licensing and activation errors
- Licensing and activation FAQs
- Red Gate tools log file locations
- Download old versions of products
- Download product prerequisites & utilities
- Support & upgrades
- Upgrading your software
- Upgrading FAQs

Using SmartAssembly for obfuscation