3 ms·
I wonder if that's the case (what was meant). When I first worked with ASP.NET 1.1, getting it to work (feature-level) with Opera often required forgoing most o
by ashmud 10y ago
I wonder if that's the case (what was meant). When I first worked with ASP.NET 1.1, getting it to work (feature-level) with Opera often required forgoing most of the "managed" control properties and using CSS/JS directly. The backend .NET code was much more of a joy to work with than Classic ASP, but the managed ASP.NET frontend portion, not as much.
- josteink 10y agoThis is the answer. Asp.net 1.1 was mostly designed for "drag'n'drop" pixel aligned "form" layouts. Optimised for VB6 devs. Definitely not webby. It wasn't until Microsoft started with asp.net MVC that asp.net finally started going somewhere properly. And that was ironically much closer to classic asp and "real" web programming than the initial versions of asp.net ever was.