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 ...