The Author Online Book Forums are Moving

The Author Online Book Forums will soon redirect to Manning's liveBook and liveVideo. All book forum content will migrate to liveBook's discussion forum and all video forum content will migrate to liveVideo. Log in to liveBook or liveVideo with your Manning credentials to join the discussion!

Thank you for your engagement in the AoF over the years! We look forward to offering you a more enhanced forum experience.

import-bot (20211) [Avatar] Offline
#1
[Originally posted by hamed]

Hello

I have employed as a developer in a software company that its team uses FoxPro
/ VB 6.0 / VC++ 6.0 as the developing tools and newly is going to migrate to
VS.NET. There is a project modified that is to upgrade a big, more than
100,000 lines DOS based program developed by FoxPro 2.x to .NET platform. The
design is as previous and the implementation will be reprogrammed. As a duty
in my job I should find an answer about the following question:

There seems to be two options in .NET to develop the program: Win Form and Web
Form. The question is if we want to redesign the application as a multi tire
program which front-end is best to choose so that we have less problems in
developing the Data Access tire. Is it better to choose Web Form and use
wrapper classes exist in ASP.NET environment or we can choose to use Win Form?
There are some facts:

1 - Windows forms have more flexibility in view and effects and users prefer
to have a Windows based interface but it is not a "must to be done" rule.

2 - Our programming team has developed VB and VFP applications and they are
more familiar with VB 6.0 than IIS, ASP and VBScript. The company can hire
some web programmers but prefer not to do it if possible

3 - They are not familiar with XML at all and I am the only person that knows
this technology. It seems I myself should develop the Data Access tire and I
am new in .NET technology but have developed several ADO based ASP
applications

4 - The new application should be able to use different data engines such as
Access, VFP, MS SQL Server and Oracle.

It seems developing a multi tire application using windows forms is highly
dependent on web services and xml communications. Using web forms as a front
end have a little flexibility but at least all data access layer will be in
the server using ADO.NET wrapper classes those are the same as ADO. But it
seems using windows forms means that we should use "Dataset" and ".NET
Framework Data Provider" that is a topic I am new in. Microsoft says either
using web forms or windows forms, there is no difference in data access layer
but I don't feel so. Am I right? What are the benefits and drawbacks of web
form and windows form at the layer of Data Access?

Thanks in advance
HamedÂ…
import-bot (20211) [Avatar] Offline
#2
Re: What are the benefits and drawbacks of web form and windows form at the layer of Data Access?
[Originally posted by arlen]


The answer to your question is not a simple one, I am afraid.

The first thing I would always recommend is to completely separate the data
access code from the UI - then you can use the same code behind either a
WinForm or WebForm application. This _does_ require more work, especially as
the tools tend to lend themselves to a more tight tie-in, but, except for the
simplest projects, ends up saving time in the long run.

As for WebForms vs. WinForms - that really depends on the goals of the
application. WinForms applications are easier to build, are more flexible and
are generally easier to use - however, WebForms are still somewhat easier to
deploy and upgrade (although there are techniques for distributing web form
applications).

If this is something that is going to run for a set number of users, where you
can control the desktops to some degree, I would tend to go with a rich
WinForms application - especially given the background and experience of your
team.

Browser applications are more "in vogue" and flashy, but I would limit
creating one unless there was a real business benefit to it.

Hope this helps,

Arlen

> Hello
>
> I have employed as a developer in a software company that its team uses FoxPro
> / VB 6.0 / VC++ 6.0 as the developing tools and newly is going to migrate to
> VS.NET. There is a project modified that is to upgrade a big, more than
> 100,000 lines DOS based program developed by FoxPro 2.x to .NET platform. The
> design is as previous and the implementation will be reprogrammed. As a duty
> in my job I should find an answer about the following question:
>
> There seems to be two options in .NET to develop the program: Win Form and Web
> Form. The question is if we want to redesign the application as a multi tire
> program which front-end is best to choose so that we have less problems in
> developing the Data Access tire. Is it better to choose Web Form and use
> wrapper classes exist in ASP.NET environment or we can choose to use Win
Form?
> There are some facts:
>
> 1 - Windows forms have more flexibility in view and effects and users prefer
> to have a Windows based interface but it is not a "must to be done" rule.
>
> 2 - Our programming team has developed VB and VFP applications and they are
> more familiar with VB 6.0 than IIS, ASP and VBScript. The company can hire
> some web programmers but prefer not to do it if possible
>
> 3 - They are not familiar with XML at all and I am the only person that knows
> this technology. It seems I myself should develop the Data Access tire and I
> am new in .NET technology but have developed several ADO based ASP
> applications
>
> 4 - The new application should be able to use different data engines such as
> Access, VFP, MS SQL Server and Oracle.
>
> It seems developing a multi tire application using windows forms is highly
> dependent on web services and xml communications. Using web forms as a front
> end have a little flexibility but at least all data access layer will be in
> the server using ADO.NET wrapper classes those are the same as ADO. But it
> seems using windows forms means that we should use "Dataset" and ".NET
> Framework Data Provider" that is a topic I am new in. Microsoft says either
> using web forms or windows forms, there is no difference in data access layer
> but I don't feel so. Am I right? What are the benefits and drawbacks of web
> form and windows form at the layer of Data Access?
>
> Thanks in advance
> HamedÂ…