idiosyncratic
Big part of it is learning something new... supporting different
browsers and more client side stuff to do with webservice.htc. see:
http://sync-io.net/go/sticky/
I can send you the project if you like.
complexity
For example, disabling radio buttons until some client event happens.
Can't be done with server code alone. However, easily done with
WinForms.
Another example, trying to impersonate a user other than Network Service
to do a task on the server side.
-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Walden H.
Leverich
Sent: Thursday, September 17, 2009 4:03 PM
To: .net use with the System i
Subject: Re: [SystemiDotNet] IIS server not sending user id
ASP.NET's idiosyncratic nature,
You say tomato I say tomato... Anything specific, or just the need to
learn something new?
ASP.NET's complexity and learning curve (IIS, JS, AJAX),
You should be able to drop something into an IIS directory and go. I see
no reason you need JS or Ajax. Sure, the make a web app nicer, but since
you don't have that in WinForms, why require it in WebForms? Start
simple.
Not to scare the developer away from .NET.
I'd think it would be more frustrating/scary to move from WinForms to
WebForms and learn all the differences than just to learn WebForms in
the first place... and don't get me started on ASP.Net MVC. :-)
a prototype UI in WinForms...
A test harness? Maybe. Just to see how something works, and actually I
prefer a command line app. Forces simplicity. A complete prototype? No
way.
-Walden
midrange.com
