Sire

I also have this problem, bug is also in latest 3.6.10. Demo here: https://codepen.io/anon/pen/OYvxrG?editors=1010

Also running v 74.0.3729.169 (Official Build) (64-bit) Could possibly be a Chrome extension then, will double check.

Verified on two clean Chrome installations in incognito with no extensions. Firefox: Works fine, no bug. Edge: Nothing works (!)

I get this as well, on a few number of requests every day (I guess 5% at the most). We're just using regular ASP.NET. `System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException'...

@tanveery I can try to fix it but I'm out of ideas. Any help?

Nulling the HelpWriter works: `var parserResult = new Parser(with => with.HelpWriter = null).ParseArguments(args);` Instead of: `var parserResult = CommandLine.Parser.Default.ParseArguments(args);`

That this is not fixed still baffles me. I'd implement it myself if I had the time.

Solution for me was to cast to real (maps to single) instead of float (maps to double). https://docs.microsoft.com/en-us/dotnet/framework/data/adonet/sql-server-data-type-mappings

Solved it. Inheriting from BlazorComponent isn't required, you can use it's interfaces instead. So in my code-behind classes I just inherit from this class that contains both the state component...

One could argue this is a problem with your application and not the notification implementation ;)