“The first version of ASP.NET, along with its integration into Visual Studio .NET, is fantastic on almost all counts. Indeed, when compared to most other version 1 products that hit the market (especially from Microsoft), ASP.NET shines bright. A few things were left out,though, or don’t work as well as they should. As the self-appointed pain in Microsoft’s ass, it’s my job to point some of them out. Here is a list of twelve issues that Microsoft needs to address for ASP.NET 2.0″ Read the article at AngryCoder.
The Dirty Dozen ASP.NET 1.0 Issues; Will they be Addressed in 2.0?
2002-11-28 .NET 10 Comments
At least angrycoder.com is all over covered with Microsoft ads.
I am often wondering where to go to see a large project implemented in asp.net. Part of the reason is probably that it is so new, but I wonder.
Does anybody have any non-MS case studies or finished projects they could point me to? And what is the difference between ASP and ASP.Net???
Gee dude…..www.gotdotnet.com is big enough ?!!
ASP.NET is using the .NET Framework.
I just finished a large intranet site (it’s internal, so I can’t point you towards it, sorry) using ASP.net. There are some things that I really like about it, and others that I wish they’d done better. Only a few of the complaints that they mentioned actually bothered me (templates are complicated), but I have a few others.
Well, I’m a big fan of .net stuff. If only ms didn’t write the horrid contraption called winforms, I’d be a happy man. I developed an asp.net realtor website. Its a pleasure to develop in, finally write a web-application feels like writing a real app. Its great. However the fact that you have to run asp.net on IIS and/or Windows kinda sucks.
Luckily it sounds like mono people will have a stable apache-hosted asp.net implementation by 2nd quater of next year. That will run on all decent platforms and I’m sure it’s gonna be way too cool.
“Luckily it sounds like mono people will have a stable apache-hosted asp.net implementation by 2nd quater of next year. That will run on all decent platforms and I’m sure it’s gonna be way too cool.”
Considering that I work for a large corporate entity, I don’t have a lot of choice what I develop in.
Having the choice of using a Windows based web server or a Linux based one for ASP.NET will be nice.
The other cool part of mono. Is that it runs on windows(in cygwin i think for now). But basicly gives on the option of using .net like one would with java. aka it doesn’t install excessive hooks into the os, so there is less chances of the mono stuff buggering up your windows install. I’ve had 2 or 3 win2k boxen suffer after .net dev kit install.
“Cross-browser client-side validation support would be nice as well, but I’m not going to hold my breath.”
ASP.NET can use client-side validation, but it uses MS DOM, but there are w3c DOM validation replacements. Just do a search.
also…. http://www.hsn.com is also asp.net. Their search function was in production under beta I. I hope that is a big enough site. :-p
You are right. WinForms is such a horrible mess. It makes swing look like a well-designed toolkit. And that is really hard. I hope Microsoft or maybe even Ximian will come up with a better toolkit. I do not mean GTK# or Qt#, but a completely new toolkit that uses the reflection capabilities of .NET and is not as bloated as WinForms. It should support layout management, scalable components, and (optional?) display lists.
Fortunately the System.Drawing namespace is nicely separated from the WinForms mess, so one will not have to write new drawing classes.
Maybe I will do it myself … 🙂