The particular update killed all our views/functionality that had "@onchange". After removing the @ and reviewing the notes to make sure that was the issue, its back up and running finally. The time before, I know we had to gut an entire file because we had some sort of duplication error that didnt exist before the update. Fun with .net ...
Rough. Is this on .Net Framework or Core?
Please Login to reply.
Netcore
Yeah, I see. Is this on Blazor? Haven't been using it yet. But it seems they still haven't found a completely stable API.