Likely installation error, but visualizer constantly throws exception about expressiontreevisualizer

[rhbourdeau]

Aha! The installation instructions you provided in the README file mentioned to "Unblock the ZIP" but I had never heard that term before and just assumed you mean "unpack the files". I did not think to look at the Wiki.

I "uninstalled" the visualizer, unblocked the entire ZIP file as you indicate in the Wiki, and reinstalled. That appears to have eliminated the problem and I am now able to invoke the visualizer while debugging.

Perhaps a direct link from the README installation instructions to the Wiki page regarding "unblocking" would be helpful for some folks.

Thanks, I'm off to work with your tool now. Much appreciated.

Side note, I'm actually working with Core in NET5. Just for reference here's my NET info, which I just realized I need to update.

dotnet --version; dotnet --list-sdks
5.0.101
2.1.202 [C:\Program Files\dotnet\sdk]
2.1.509 [C:\Program Files\dotnet\sdk]
3.1.100 [C:\Program Files\dotnet\sdk]
5.0.101 [C:\Program Files\dotnet\sdk]

[zspitz]

Firstly, thanks for a well-written and comprehensive bug report. It's not something that can be taken for granted.

Also, the NuGet package isn't intended for use as debugging visualizer in VS; AFAIK debugging visualizers can only be installed by copying them into the appropriate folders. It's purpose is only for the visualizer's UI to be used in other applications.

What precise version of .NET Core are you using (dotnet --version; dotnet --list-sdks)? I am trying to reproduce on my machine.

Also, you didn't mention this, but you may need to unblock the ZIP file; instructions for doing so can be found here.

I don't see anything else wrong with the steps you took to install the visualizer, unless when targeting .NET Core 3.1, it's actually going to use netstandard.

Update

I am unable to reproduce the bug, with .NET Core 3.1.407 (the latest patch version of .NET Core 3.1).

[zspitz]

Great to hear.

Perhaps a direct link from the README installation instructions to the Wiki page regarding "unblocking" would be helpful for some folks.

Already done.