3 ms·
C# and SQL I might agree with. But ASP.NET and MVC = stable? All the hidden view state and POST backs to re-render the UI... terribly difficult to troubleshoot
by matchagaucho 10y ago
C# and SQL I might agree with. But ASP.NET and MVC = stable?
All the hidden view state and POST backs to re-render the UI... terribly difficult to troubleshoot and support in my experience.
- UK-AL 10y agoThat's ASP.Net WebForms which is basically very old and legacy.
- pjmlp 10y agoI wish. Even this year I was getting some SiteCore requests, which I didn't accept, but version 6 was largely built on top of forms. I haven't bothered with it since version 6, so I don't know how well it has moved into MVC world.
- yareally 10y agoSeconded. Sadly, our tech stack at work still includes some webforms cruft and I have a few friends at other companies that also still have to deal with them. Could be worse I guess...I know someone that still has to put up with classic ASP. Thankfully I work with backend stuff at my job currently or I'd probably go crazy dealing with a mishmash of mvc and web forms. Webforms are not super easy to get rid of if you weren't careful on how you coupled to them, so I think some code is still being added to ours.
- flukus 10y agoSame with sharepoint, although apparently that supports MVC now too.
- yareally 10y ago> "All the hidden view state and POST backs to re-render the UI... terribly difficult to troubleshoot and support in my experience." You're confusing webforms (with viewstates) and .net MVC, which is stateless. http://stackoverflow.com/questions/23623229/what-is-the-equivalent-of-viewstate-in-asp-net-mvc http://stackoverflow.com/questions/23623229/what-is-the-equi...