Export tracepoints to auto-created file instead of prompting for file to save

codekaizen 5 years ago updated by Omer Raviv (CTO) 4 years ago 3

Exporting tracepoints to Excel is wonderful... until I'm hit with the "Save As..." dialog. This prompt introduces significant friction to the workflow. I often don't need to persist the exported data beyond the immediate debug session, but when I do, I can do a "Save As..." in Excel. If the "Export" function auto created a temporary file and opened Excel on it, it would be much smoother and I wouldn't learn to dread exporting.

Under review

Thank you for the request, that makes perfect sense and we'll try to accommodate it soon.

By the way, you'll notice a couple of nice improvements in OzCode v2.1: the style of the Excel file is improved (dates turn into Excel dates, Auto-Filtering turned on by default, and the values within the message appear in bold for readability.

Another nice improvement you'll find in v2.1 is the ability to Export any collection (IList, IEnumerable, etc) to an Excel file via the Magic Wand (each object's field and properties nicely formatted as columns in Excel). The latter already behaves as you requested - Excel is opened immediately without having to go through a Save As dialog.

Again, thanks you very much for taking the time to give us your feedback!

This issue has been fixed. The fix will be deployed as part of the OzCode v2.1 update.