-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System.NotSupportedException in the newest Visual Studio #81
Comments
Hello! Thanks for letting me know about this - glad the extension has been useful! Because it installs with an MSI, you have to uninstall it via Add/Remove Programs - could you give that a try and let me know how you get on? Cheers! Steve |
@SteveWilkes Hi, Steve. Thank you for the response! What do you think could be causing this? |
Hmm - looks like we've run into this .NET 5 breaking change, which is causing issues elsewhere, too. I assume (confirmed - see 'The VisualizerObjectSource') the VS debugger uses You can enable it in Debug only using: <PropertyGroup>
<TargetFramework>net5.0</TargetFramework>
<EnableUnsafeBinaryFormatterSerialization Condition=" '$(Configuration)' == 'Debug' ">
true
</EnableUnsafeBinaryFormatterSerialization>
</PropertyGroup> There are security considerations to doing this, but I suspect unless you're using Thanks again for bringing this to my attention, I'll have a look to see if there's anything I can do to work around it on my end, although I suspect it's down to how Visual Studio Debugger Visualizers are implemented, so it'll be one for Microsoft! |
Hello! I've now had a reply on Microsoft's Developer Community regarding this, which confirms it's ASP.NET Core 5-specific, and is down to a change in Visual Studio. The recommended fix is to enable the binary formatter in debug as described above. Cheers, Steve |
Hi! Sorry for being late! |
OMG!, this one should be on the readme.md. I'm installing and uninstalling things for two days, blamed my anti-virus and stuff BCS of this. |
Sorry about that @mhamri - I've updated the readme as you suggested. All the best, Steve |
Sounds like there's an issue with the installer too, if uninstall is not removing the visualizer from VS completely. Another report of this issue: https://stackoverflow.com/q/67569999/24874 |
Thanks for the heads up on that one, @drewnoakes - I've added an answer to the SO question. The poster didn't actually run the uninstaller as far as I can tell, so I think it's probably fine. |
Using VS2019 16.8.5 I added the
|
I've seen that sort of error happen @pantonis - if something goes wrong with the debugger (which can be the visualizers, and can be the way the visualizers handle the debugger in particular states - it's weird and difficult to diagnose), it can throw those errors until you close + reopen Visual studio. |
Hi there! Extremely useful extension!
![image](https://user-images.githubusercontent.com/26527405/100415970-90585a80-3092-11eb-8e69-50412f25d7c9.png)
I've been using it for quite a while now, but after I reinstalled Visual Studio 2019 (I'm on version 16.8.1 right now), whenever I click on the magnifier button, I get the following error window:
I was going to try uninstalling and then installing the extension again, but the "Uninstall" button is grayed out:
![image](https://user-images.githubusercontent.com/26527405/100416052-c72e7080-3092-11eb-8639-19004e39383f.png)
I'd appreciate any help.
The text was updated successfully, but these errors were encountered: