Despite the loud groaning sound we all just heard, there is a LOT of WebForms code out there. I also meet people who are moving off of WinForms and asking if their only choice is MVC. Despite the banter about architecture, some sites naturally feel like pages rather than a resource based applications (WebForms vs MVC... forms over data vs Music Store in the early examples).
Are there modern 2018 best practices for WebForms? Are there new features devs probably haven't paid attention to now in WebForms (model binding and async come to mind for me, but I admit to not being well versed).
What do you avoid today? Should you immediately go shut off viewstate somewhere? Should you avoid using Session? What else? What should you know to either build a greenfield WebForms app or "clean house" on an existing app so as to modernize it for today's desired attributes of an application.
I heard Jeff Fritz knows a thing or two about WebForms.
csharpfritz
commented
6 years ago
Despite the loud groaning sound we all just heard, there is a LOT of WebForms code out there. I also meet people who are moving off of WinForms and asking if their only choice is MVC. Despite the banter about architecture, some sites naturally feel like pages rather than a resource based applications (WebForms vs MVC... forms over data vs Music Store in the early examples).
Are there modern 2018 best practices for WebForms? Are there new features devs probably haven't paid attention to now in WebForms (model binding and async come to mind for me, but I admit to not being well versed).
What do you avoid today? Should you immediately go shut off viewstate somewhere? Should you avoid using Session? What else? What should you know to either build a greenfield WebForms app or "clean house" on an existing app so as to modernize it for today's desired attributes of an application.
I heard Jeff Fritz knows a thing or two about WebForms.