I deployed a raw Blazor Client application for testing. I made a div element onmousemove event so that moving the mouse on div's content update x and y variables and show them to the user, When I deploy the app to IIS and use Edge browser to view this page,
the x and y update very slowly while when I use Chrome or run it on IISExpress in visual studio the update is fast and smooth, Does a blazor client app supposed to be as fast as a client side framework such as Angular? So why edge not as fast? My other question
is: when I Refresh the counter page I get 404 not found from IIS, Why is that and is there anything to do so that all pages in the website Refresh correctly?
I created a rule in IIS Url Rewrite Module that redirects all non file urls to index.html but when this happens I got the error: Sorry, there's nothing at this address.
This error shows in the @body section of the layout page, And is not a IIS generated error. So maybe something is missing in Blazor Startup, Spa Fallback!?
Member
51 Points
292 Posts
Blazor Client side deployed but two problems
Nov 23, 2019 02:49 PM|mz1378|LINK
Member
51 Points
292 Posts
Re: Blazor Client side deployed but two problems
Nov 23, 2019 08:40 PM|mz1378|LINK
This error shows in the @body section of the layout page, And is not a IIS generated error. So maybe something is missing in Blazor Startup, Spa Fallback!?
Member
51 Points
292 Posts
Re: Blazor Client side deployed but two problems
Nov 24, 2019 07:33 AM|mz1378|LINK