Re: FN-FORUM: .Net Form Posting - Vaguely OT

date posted 25th February 2008 17:48

Ben Moxon wrote:
> It's like any platform, once you understand the way of working that
> works in alignment with the design of the platform it's pretty easy to
> work with. If you don't it's hard. Asp.net has one very flexible form
> rather than lots of inflexible ones - lets face it your users are only
> ever going to work with one form per page at a time anyways.

Now that's where I'd have to disagree - one experience I had was with a
company trying to convert a page to .NET that had a "search" form at the
top of every page as part of the header, and then had other forms on
some pages for signups to mailing lists, promotions and the like. In the
end they finally decided to have to remove the search form from each
page, and have a one-off search page - which kind of lost some usability.
> Mostly it's pretty convenient, sometimes it's a bit awkward, but there
> are some solid re-use advantages to a bunch of the stuff it does and
> it works around the whole page state thing very nicely.
>
> I'm not overly enamoured with it, although I have loads of experience
> with the platform, but if you understand it well enough it's certainly
> the equal of any other web plaform. Except Rails, obviously, that has
> no equals- only imitators :-D
>
And I do agree, that it's just like any platform that has its good bits
and bad bits. Even Rails has issues (the thing about the naming of
tables and ID columns springs to mind) - I just seem to see a lot of
questions on how to do things in .NET that are easy on other platforms.

Alex.
http://www.ozbon.com