Making sense of large collection of data in Visual Studio
The thing about putting “Part 1” in the title of a blog post is that you sort of have to write at least a “Part
Have a bird’s eye view of what’s happening when your code runs:
Intuitive extension for your Visual Studio IDE
powerful heads-up display, advanced search inside objects, LINQ query debugging, side-by-side object comparisons and more
Easy to understand dashboard right in your browser for production environment monitoring and effective bug triage
After you’ve made your hypothesis – OzCode can help create and test your fix:
Live edit code in your IDE in debug mode and see how your changes affect the results by traveling to the future
Automatically get the snippet of code that threw an exception, then edit, test and deploy – right from your dashboard
Analyze your queries and see how items are passed through the LINQ pipeline
Get a graphic representation of your LINQ pipeline
Understand exactly how what went in and came out of each LINQ operator
Predict how your code will execute, prevent potential bugs, know everything with predictive data-tips
Edit the potential futures and travel back and forth through iteration loops
Visualize the evaluation of your data and your code
Coding is rarely a one person job;
Get all the tools you need to collaboratively debug
Use LiveShare in your Visual Studio IDE to debug together
Use the collaboration panel in your browser dashboard to co-debug your production environment, add questions and ask comments right next to your code and statistics
The thing about putting “Part 1” in the title of a blog post is that you sort of have to write at least a “Part
Dealing with large collections of data is a pretty common occurrence when debugging C# applications. As data science becomes more mainstream, this generalization is unlikely
This article is originated from Michael Shpilt’s blog, Michael’s Coding Spot. Deck the halls with boughs of holly, it’s that time of the year again! The end of the year is