CODEWITHSUNDEEP
javaasp.netsql-serverwebclient
David Xavier
David Xavier

Reputation: 91

Windows Client vs Web Client

I have a discussion going on in the organisation where I am employed as a consultant. The discussion revolves around the replacement of an application built using VB6(MDI) thick client.

This application has around 100 screen + 40 reports. Used by approx 400 users the reports and the data are pulled using inline queries while the db structure is pretty normalized. the rest of the code is pretty bad.

While discussing replenishment strategies we are throwing around a few ideas.

  1. J2EE Web application running on Web sphere using Crystal reports for Reports.
  2. ASP.NET web forms web application using crystal reports for reports.
  3. Windows Client application (WPF/Win-forms) with reporting services for the reports.

While I don't want to start a flame war (Dot net vs. Java or WEb vs. Desktop) it would be nice to know the community thoughts on the matter. Just to be upfront I feel that option 3 maybe the best version, but I would like to know the opinions of others.

Upvotes: 2

Views: 680

Answers (6)

gbn
gbn

Reputation: 432230

From a deployment and support perspective, 1 or 2: no client install needed.

I'd suggest Winforms only if you need complex presentation or flow that would be hard to capture in a web page. That said, there is Flash and Silverlight etc for that...

Upvotes: 1

LeftyX
LeftyX

Reputation: 35587

It's never easy to convert an "old" applications to a different platform. It takes time to learn new technologies and implement it in the best way.

Since you're familiar with VB6 I would suggest you to consider ASP.NET MVC using VB.NET as a programming language.

I've developed a few WebForm web apps in the past but I've never felt really comfortable with it: - too many events to manage - hassles with postbacks and viewstates

ASP.NET MVC is, let's say, more intuitive. I love it. You can add jQuery (or another javascript framework) to obtain a more fluid interface. As a reporting tool I've used and hated Crystal Reports. I much prefer the RDL/RDLC format (reporting services). You have a designer integrated in Visual Studio and can even build the XML from scratch.

Upvotes: 1

iDevlop
iDevlop

Reputation: 25262

I would also add to the excellent remarks here, that part of your considerations might involve the system "statbility". If your app is going to require a frequent updates, then a web approach might be better. If the app is going to be stable, a desktop client is probably going to be much cheaper to build.

Upvotes: 1

Alan B
Alan B

Reputation: 4288

How heavy is the VB6 app with third-party controls and the like? Could you replicate those in a browser-based UI ?

Upvotes: 1

Joel Martinez
Joel Martinez

Reputation: 47749

To add to karianna's response ... Be Careful. You will more than likely fall into the Second System Effect. A better approach would be to leave the existing system in place, and just make new features with one of the new technologies and slowly start migrating. Don't plan on doing a pick up and drop migration to "the new version"

Upvotes: 1

Martijn Verburg
Martijn Verburg

Reputation: 3305

A key question you have to ask/discover is whether or not you really need to replicate the existing functionality. You'll probably find that with changes in the business workflow and improvements in technology that you don't need to build a hundreds of pages and 40 reports solution.

If you do more or less have to replace it then any of the 3 technologies can do the trick. They key is to prototype. Try each of them out before you settle on one.

Upvotes: 1

Related Questions