I was working on an older solution that was migrated to a new workstation when I received the above error. My fix was to update my AspNet.ScriptManager.jQuery NuGet package to the latest stable version. It was at version 1.8.2 and I updated it to version 3.7.1. Cleaned/rebuilt and then restarted the site in VS - the error went away.