3 ms·
ASP.NET WebForms is absolutely a framework and a heavyweight one. It tries to hide the details of http and html as the grandparent says. I for one don't care fo
by SideburnsOfDoom 13y ago
ASP.NET WebForms is absolutely a framework and a heavyweight one. It tries to hide the details of http and html as the grandparent says. I for one don't care for that, I prefer a lighter weight framework which works with http rather than hiding it. ASP MVC is lighter weight than webforms, and Nancy or ServiceStack is even lighter weight.
Some things like making an endpoint that servces json and xml responses is almost trivial on Nancy or ServiceStack, easy in ASP MVC with WebApi, and a pain in webforms.
- graycat 13y agoThanks. As I wrote above, as far as I know, I'm not using WebForms and am just using basic IIS and ASP.NET. From what I understand, what I'm using is lighter weight than MVC or anything else being discussed here. So far, I see no problems with what I'm doing. E.g., for the MVC architecture, I have a server farm and software architecture, and it's simple and more than enough.
- SideburnsOfDoom 13y ago> as far as I know, I'm not using WebForms If you have "event handlers" like "Page_Init" in a .apsx.vb file then you are using web forms. No other framework has these. They were an attempt in the late 1990s to make the web look like winforms. it worked, to a degree. > what I'm using is lighter weight than MVC I doubt it. > I see no problems with what I'm doing. That's a different question; I'm sure what you're doing is workable.
- graycat 13y agoThanks! I needed that!