I learned today that you should never update visual studios. With each new update, they decide to change what appropriate calls look like, breaking everything you wrote that doesn't meet their new centralized standards.
All methods henceforth will end with VSgfy()
#plebchain #codingsucks #iwanttostabsomeonewithCsharp
🤔 What exactly do you have problems with? I'm working with VS since VS2005 and never had problems after updates.
On the other hand I had some problems after installing it on new systems due to missing legacy frameworks/runtimes that weren't delivered by default with the newer versions.
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 ...
