Your comments

Thanks! This error seems to suggest that earlier on, OzCode failed to load its Probe assembly into the debuggee. That might appear earlier in your log file?

Thanks for the comment, Hbx! Can you please send us your latest log files from %TEMP%\OzCode\Logs to support@oz-code.com?

No, but indeed the time difference between v3.5 RTM and v4 EAP may be short. We are still ironing out some issues with the new crazy-fast search. Note that there will be at least one more update to v3.5 EAP before it RTMs, which will also include the Conditional Search feature shown in the recent webinar.

Hi there,


OzCode v3.5 EAP was released in September and last month we released a webinar which shows some of the cool new features in the EAP (especially around to 8 minute mark and onward). However, the super exciting news is that OzCode v4 will be a monumental jump forward for us, as we've spent the past year and a half cooking up something very special. The first video covering some of the features that are coming in OzCode v4 has already been recorded and will be released in January 2018 on the Channel9 "Visual Studio ToolBox" show. Please stay tuned to our blog and social media as we'll definitely be sending out updates when it is released.

Thanks for the clarification, Jakub. That makes perfect sense.

Hi Jakub, the fact we're still showing you values on return values is something we considered to be a feature rather than a bug - or rational is that return values are so important that you'd always want to see them. I understand that you do not feel this way, and would prefer to have the feature completely off?

Ah, I forgot to mention, the QuickWatch window can be opened by going to Debug->QuickWatch (usually Shift+F9 is the shortcut). This is for when you want to explore some variable in a modal dialog (similar to the Visual Studio Watch window).

Hi Michael,


Ah, if you want a persisted window with an easier way to look at the LINQ debugging information, which doesn't disappear when you click away, you can use the LINQ Analysis window for that. This is covered in this video: http://o.oz-code.com/videos#202603006 and also in my recent Channel9 video - I begin talking about the LINQ features around minute 31. Please let me know if you managed to use it and if it was helpful.


Finally I wonder if I could ask for a small favor - if you enjoy OzCode, would you please consider taking a moment to leave a short review on our Visual Studio Marketplace page? It would mean a lot to us!


Thank you and have a great day,

 - Omer Raviv, CTO, OzCode

Hi,
Fortunately, you can always use the QuickWatch window which will enable you to inspect a Collection in a separate window. Is that what you were looking for? We also thank you for your kind words.

Hi Steve. Thanks for the report! As it turns out, I just tested this and the problems occurs just the same on an instance of Visual Studio that does not have OzCode installed. As such, you may want to report this issue on the Microsoft feedback page.


FYI - the problem occurs because enumeration the Results View requires the System.Threading.Thread type to be already loaded into your application. Thus, if you were to add the line of code "var myThread = Thread.CurrentThread.ManagedThreadId;" to your console app (for example, as the 1st line of Main()), that will solve the problem for you.


Hope this help!