Good point Craig. I would still prefer to create a WinForms client and a Windows Service that runs on a remote server. The service would handle all data-layer functionality, including iSeries ADO provider, while the client would be just that, a client to the windows service with some UI components. ( see ISBN 978-0-7356-2433-7 )
-----Original Message-----
From: systemidotnet-bounces@xxxxxxxxxxxx [mailto:systemidotnet-bounces@xxxxxxxxxxxx] On Behalf Of Craig Pelkie
Sent: Wednesday, September 16, 2009 5:00 PM
To: .net use with the System i
Subject: Re: [SystemiDotNet] IIS server not sending user id
A big part of the deployment problem with WinForm apps would be getting the
.NET and/or OLE DB providers installed on everybody's PC. That can be a big
problem, especially with the IBM DB2 .NET Provider. If the end-user PCs are
at a down-level version of System i Access (say, at V5R1 or V5R2), you need
to update the PC to at least V5R3, then run Selective Install to install the
.NET Provider. Then you need to be sure to install the Service Pack, there
were some issues with the .NET Provider where it would not work until the
Service Pack is installed. These types of updates cannot be pushed to the PC
using the one-click deployment. If you have a complete inventory of, and
control over, the end user PCs, WinForms might be considered.
But usually, it makes a lot of sense to simply go with a web app to begin
with.
Some alternatives would be WinForms that call back to the server using web
services. That way, the database access can be kept on the server.
AJAX in .NET is a good solution to get better interactivity in the browser,
but it looks like Silverlight provides the best solution for interactivity
in the browser.
Craig Pelkie
----- Original Message -----
From: "Thorbjoern Ravn Andersen" <ravn@xxxxxxxxxx>
To: ".net use with the System i" <systemidotnet@xxxxxxxxxxxx>
Sent: Wednesday, September 16, 2009 2:12 PM
Subject: Re: [SystemiDotNet] IIS server not sending user id
Lee Arrison skrev:
Yes, it does need to be a web app. It's going on our intranet, not
installed on the users pcs.
Just a thought. I belive .NET has a "one-click" web wrapper for an
application (corresponding somewhat to the Java Web Start technology).
If it can do automatic updates, would it be usable?
midrange.com
