-
Notifications
You must be signed in to change notification settings - Fork 210
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
Testing the WebAssembly components and service (ch15-blazor-wasm.md) #60
Comments
A little help please. |
I have updated the online section with new instructions and made the same changes to the |
Switching to the WebAssembly component I was getting weird errors in the browser's console trying to get this to work.
I found that others had similar issues and followed their advice and got it to work. Basically, I closed Visual Studio, then deleted the folders underneath the Northwind.Blazor.Wasm project's obj and bin folders. Restarted Visual Studio and it worked fine. This is where I found the advice: I don't really have a lot of confidence in Blazor as a platform yet. I feel like it's still going through some nasty growing pains. |
I agree with you. To me, Blazor is still an "unstable" platform both in that it has more bugs than alternatives like MVC and that it is still evolving. .NET 8 introduced huge changes in Blazor that meant the way I had designed my step-by-step instructions for the .NET 7 edition then broke with .NET 8 in ways that I discovered couldn't be easily fixed. When I first looked at the issues readers like you were having I tried to find some simpler fixes but ended up having to almost rewrite that whole section. Blazor feels too much like the old Web Forms ( I'm sorry I wasn't able to provide a solution earlier. I appreciate how frustrating that must have been for you and others. Thank you for your patience. p.s. I will add the information you found about the |
The text was updated successfully, but these errors were encountered: