Yes. Click Leave us a private message on our UserEcho community page. All communication marked as private is only visible to you and Ozcode engineers.
All of Ozcode’s major features can be disabled independently.
Check the dialog under Ozcode’s Options menu.
Simplify will only show you historical results in VS2013 and VS2015.
If you’re using VS2012 or VS2010, you will only be able to see a predictive analysis of the next statement to execute (highlighted in yellow).
Yes. Under Ozcode’s Options menu, uncheck the first checkbox.
Ozcode officially supports Visual Studio 2015, 2017 and 2019. Ozcode doesn’t work in Express editions but does work on the free Visual Studio Community Edition.
Currently, Ozcode only supports C#. We plan to add support for more languages in the future.
For Ozcode’s EULA, click here.
Tracepoints (aka non-breaking breakpoints) are placed on lines in your code where you want to add a dynamic log entry. They are similar to breakpoints, in that they are lines in your code where you want to inspect data, however, instead of stopping the application flow, you output data to logs.
For more details, please refer to Dynamic Logging with Tracepoints in the Ozcode Production Debugger documentation.
Working with tracepoints and dynamic logging involves the following steps:
- Create a tracepoint session
- Select a class
- Set your tracepoints and the corresponding dynamic log entry
- Collecting data
For full details, please refer to Working with Tracepoints in the Ozcode Production Debugger documentation.
Tracepoints do not put any noticeable strain on system memory.
In case a tracepoint is repeatedly hit with high intensity, the tracepoint session will stop collecting hits after a set duration or number of hits which you can control using the cog icon on the Start collecting button. For full details, please refer to Collecting Data under Working with Tracepoints in the Ozcode Production Debugger documentation.
“Dynamic logging” refers to silently adding logs to your live systems without requiring changes to the code. In Ozcode, this is done using Tracepoints.
For full details on using Dynamic Logging with tracepoints, please refer to Working with Tracepoints in the Ozcode Production Debugger documentation