Click on the OzCode menu and select Create a Dump and Open it to create a snapshot while debugging!
By now we all know that OzCode’s time-travel will save you from doing Step Overs (F10) while debugging.
But what about Step Into (F11)?
Debugging is full of Step Into‘s and Step Outs (Shift + F11). Each time you step in or out of a method, you lose context. Your mental load increases. Time-travel debugging allows you Step Into a method, without changing the yellow debugger line:
We call this Go to Execution. Here are some features it allows:
The regular search functionality is great to search for text in expression properties and members, and it’s been recently radically improved. But, what if you want to search based on some kind of logical condition? For example, searching for customers with age between 25 to 30. Or, searching for companies with over 20% income increase? You’ll need some kind of predicate for that purpose, sort like you would use in LINQ Where clause.
This is exactly what Conditional Search is about! We are now allowing you to search a collection, according to custom logic.
How it works
First, hover over a collection object (any IEnumerable will work):
In this example, the search is a match for each customer whose BloodType starts with “A”.
The Predicate can be any C# expression that returns a bool, when hovering over IEnumerable. You can include logical expressions and whatever complicated logic crossed your mind.
For example, if T is a Company, you might write:
Everything works, as long as it’s managed code.
When debugging huge collections, use OzCode’s Filter featurefeature to focus on the interesting items
With OzCode’s Quick Attach, you can bind a key to quickly Attach to Process!
OzCode’s Trace features makes multi-threaded debugging much easier!
Have a look at some of our popular instructional videos