Re: IIS server not sending user id

The three reasons for a starting .NET developer to write a Winforms app
first would be:
- ASP.NET's idiosyncratic nature,
- ASP.NET's complexity and learning curve (IIS, JS, AJAX),
- Not to scare the developer away from .NET.

If a web app is required I would still code the DB code into a DLL,
write a prototype UI in WinForms, then once everyone is happy with the
prototype functionality port over the UI to ASP.NET.

-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx
[mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Walden H.
Leverich
Sent: Thursday, September 17, 2009 11:48 AM
To: .net use with the System i
Subject: Re: [SystemiDotNet] IIS server not sending user id

Anyway. I would recommend first coding the app with Widnows Forms
and then porting the code over. This way you're tackling your
db and asp bugs separately.

FWIW, I'm going to totally disagree with that. I see _no_ reason to
write a winforms app. If you want to separate your web issues from your
db issues, write a web app that has no db access first. There are _very_
few reasons to write winforms apps, direct hardware access, gaming, and
distributed compute requirements, being among them. But any typical
"business" application should be browser based these days.

-Walden