Blazor Wasm Client debugging issues

Question

Blazor Wasm Client debugging issues

EuroEager2008 21

Debugging a web assembly client application is quite different to a "normal .Net" application (e.g. Blazor server side).
Examples:
Intellisense in watch window doesn't work.
Hexadecimal display in watch window is available, but does not work (always decimal), writing debug message to output windows by System.Diagnostics.Debug.WriteLine() does not work.
Objects are shown differently in watch window (e.g. string is shown with single-quotes instead of double-quotes.
Edit value in watch windo is available, but edit/enter shows an error message box: "Invalid expression (Invalid expression)", quite sense-less to me.

I am pretty sure the list could be longer, but these are for now.

Is there something weird with my setup?
Asking because I haven't seen anything on web regarding these issues from other devs
(Windows 10 20H2 (19042.746), Vs2019 16.8.4, .Net 5)

Accepted answer

0 additional answers

Your answer

Answer 1

Ahmed Alejo 76

@EuroEager2008 your setup is ok, the problems you mentioned exist and are accurate as of the time of writing this.

Other developers face this as well,

But most are still in the process of getting used to Blazor, overwhelmed by its hype, they have not gotten so deep that issues with debugging would be a focus.
While some(that have gotten past the learning curve) simply focus on requesting major blocker feature like HotReload similar to https://www.livesharp.net/blazor and consider it a new tech with some issues.

Hopefully with an HotReload, that's even better than Livesharp, debugging variables would be less necessary.

EuroEager2008 21 Reputation points

2021-01-23T13:39:52.887+00:00

Thanks, didn't even know about hot reload in general or LiveSharp in particular (I have anly brief experience developing web at all).
Haven't tried it yet, but will soon.

Anyway, it strikes me that MS should at least make the dev as seemless as possible (paying a lot of money for MSDN VS), fixing simple things like vs debugging issues.

You say dev's request some kind of HotReload (similar to LiveSharp), if you mean requesting MS to include in VS I fully support it (providing previewing LiveSharp is pleasant) (where can I vote?).
Ahmed Alejo 76 Reputation points

2021-01-24T23:22:24.67+00:00
A user almost pleading for improvements: #27517
he is been using or trying to use it for 2 years

Microsoft Team created an Issue since Jan 2018: #5456
I hopped on to it now because it is a bit more matured but not hot-reload is "wait" of time.
You can give thumbs up there to prioritize.

NOTE: The HotReload was planned for December 2020 with the NET 5.0 release it was postponed to end of 2021 with .NET 6 Release.
also note that there will be non-production-ready previews and release candidates until then.

UPDATE:

issue #5456 has been closed for comment they seem to not want more feedback as they know they need to fix it.
You can always create a new issue which they will be closed referring #5456

Good luck mate

Share via

Blazor Wasm Client debugging issues

UPDATE:

0 additional answers

Your answer