The primary difference is where your .NET code is running: with Blazor Server, it’s 100% server-side; with a hosted Blazor WASM application, .NET code is running on both the server and the client (though the server can run any other language or framework you want too). From what I read I understand Blazor Server side … Read more
onkeypress is fired only for character keys. onkeydown will fire for all keys pressed. I found some explanation of differences between all key events here Try it with onkeydown and it worked: <input type=”text” @onkeydown=”@Enter” /> In the event handler you will have to do this (notice that I check for both Enter and NumpadEnter … Read more
I finally made it work. I did everything that guide said, except for the project file which I changed to this: <Project Sdk=”Microsoft.NET.Sdk.Web”> <PropertyGroup> <TargetFramework>net5.0</TargetFramework> <UserSecretsId>*****</UserSecretsId> <UseBlazorWebAssembly>true</UseBlazorWebAssembly> </PropertyGroup> … But I have no idea if it is correct when official upgrade guide says to use: <Project Sdk=”Microsoft.NET.Sdk.BlazorWebAssembly”> instead of: <Project Sdk=”Microsoft.NET.Sdk.Web”>
Maybe you can try running your application from command prompt: dotnet watch run debug
I have tried calling StateHasChanged() – instead of InvokeAsync(StateHasChanged) – in a Timer’s Elapsed event, and it works as expected That must have been on WebAssembly. When you try that on Blazor Serverside I would expect an exception. StateHasChanged() checks if it runs on the right thread. The core issue is that the rendering and … Read more