Computers, Personal, Programming, Technology, Web Programming

ASP.NET sucks

I recently bought a book about ASP.NET: Pro ASP.NET in C# by Apress, mainly because when I was looking for jobs there were lots of ASP.NET jobs advertised. And I have to say I have no idea why. Part of the problem may be that is book isn’t very good (there are bits of vague contradictions and a general obsessive (and inaccurate) preachiness about it) but I think there are major limitations to ASP.NET.

Firstly the inability to post to a different page. Who the hell decided that was good idea? I know it can be faked but that’s just silly. And you can only really have one form on a page. Well you can only have one “rich” form that ASP.NET can access in a clever and high level way.

I’m assuming people will disagree with me (if not, why is it so popular). If you do, please explain why ASP.NET is supposed to be so amazing because I don’t see it…

Updated – Clarifying my position on

103 thoughts on “ASP.NET sucks

  1. Sucks big time. BIG TIME. Problem is that management don’t have a clue either way. They buy into the buzzy MS marketing b*lls**t. Let’s put it this way. If these guys took their cars for a service they wouldn’t restrict the mechanic to pliars and ring spanners and expect them to do a good job. Hey! Managers! Do you think we can get back to basics and define the job first before we decide on what tools we need to deliver it? Dump this idiotic, obsessive .Net/C# fits all crap and, while you are at it, learn something about the job OR leave the key technical decision making to those who know what they are doing.


  2. Also, a warning for all serious developers. If you want a high performance website – do not base it on the membership provider. Again, you don’t have full control over it.


  3. I’ve been a professional C++ programmer for the last 10 years. Recently I got into C# and I must say I like it. Then I tried out ASP.NET and I was disappointed. I think MS should ditch ASP.NET and go with something entirely new….something less visual and more programmatic. Making dynamic pages in the designer seems like the wrong approach. The designer is great for static pages though, but so is Front Page. For dynamic pages I would rather do straight up coding in C#.


  4. I’m glad I found this site. It’s good to see I’m not alone in my frustration with ASP.NET. I’m a professional web developer. I have experience working on applications in ASP, PHP, ColdFusion, and JSP. I recently decided to try out ASP.NET to see what it’s all about (I started out with an open mind, and even a bit enthusiastic about it), but after working with ASP.NET for a short while I think it is essentially made for two types of people: (1) Windows application developers that want to build web applications without having to learn the basic grammar of user agents, and (2) kids straight out of school that don’t know anything yet and can be coached (i.e. brainwashed) into developing web sites ASP.NET style. — If phrases like ‘semantic markup’ or ‘progressive enhancement’ have any meaning or value to you – then forget about ASP.NET. If you like being able to control what you send to the client, then forget about it. ASP.NET is basically an HTML generator, designed for people who are not web developers, to build applications to be distributed via HTTP.


  5. Asp.Net suck when you are starting out Period. Not because it is not comprehensive but because there is no documentation and examples on anything useful for every day development. Something that takes only two minutes to implement will take two weeks of google search. Finally you get a half-baked answer you have to settle for. Some of you think that drag and drop solutions are bad and I think you’re all friking retards. Perhaps you can sit on your fat ass and potts around writing everything from scratch while some one pays your salary. Wait till you are in business for yourself. Customers want everything done yesterday and they want it for free. The only way I can make some money is if I get it done fast. Some stupid retard from the stone age came up with the idea that we still should use notepad to create web applications and all the sheeple repeats it as if it was THE way to get things done. ..But getting back to Asp.Net. It sucks, it blows chunks! You can’t find one decent book to go beyond the basics that you can actually use in real life. The community is possibly the worst of its kind. Unless you know some one who can show you the ropes, prepare for at least 2-3 years before you’re up and running. The amount of things you have to commit to memory just to create a simple application is mind blowing. I got into it because it was on top of the job market and seemed to offer the best pay and provide the best opportunity.


  6. a website with site error site error site error… duh. Must say that the error page is kinda cool. Keep it simple for simple sites. ASP or PHP. Thats simple enuf.


  7. I’ve returned 18+ months later (see my comment around Oct 2007), and although I’m definately a better ASP.NET developer (nearly 3 years development) I’ve still spent all day messing around with control validators. Why oh why am I wasting my time with this stuff?!? Am I alone in constantly trawling the ASP.NET forums to find answers to some ridiculous problem that some other poor fellow has been facing?!?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s