none
which is better Windows or web forms ? RRS feed

  • Question

  •  

    Hi,

    Background Info.

    I’m a .Net developer, currently working in my University electronic registration System.

    We are using the n-tier architecture in this system.

    We just finish the phase of developing the “Portal” that’s enable students to register online, we develop this module as a web form , using ASP.NET 2.0

    Currently we are in the moment to develop the modules of the system that registration employees want to use in their offices.

    My Key question based in your experience, which is better to use, Windows Application, or Web forms? For the employees.

    Tuesday, March 4, 2008 11:22 AM

Answers

  • Hi,

     

    Welcome to the MSDN forums.

     

    If your application will be used by only a department and the department is connected using LAN, go in for a windows app. Some advantages of a windows app are rich UI, high performance and robustness, can use full-trust model etc.

     

    If your application will be used by the general public,i.e people outside the organisation or employees who want to access the app outside the office: go in for web application. Some advantages of a web app are wider audience, easy deployment. However you will have to deal with issues like cross-browser app, slower performance as compared to windows.

     

    http://dotnet.celeritas.com/Windows-or-Web-Application.html

     

     

    HTH,
    Suprotim Agarwal

    -----
    http://www.dotnetcurry.com
    http://www.sqlservercurry.com
    -----

    Tuesday, March 4, 2008 11:49 AM
  • Mohammad

     

    I would have to say that there is alot to consider here.  Some of the things to consider in your platform decesion should be but not limited to:

     

    • Bandwidth of user
    • Users expectation of rich application
    • Location of users
    • System requirements of the users

     

    Web applications have come along way in the past couple years, but they are no where as rich as a windows client.  Windows clients are nice, but provide you with a level of complexity that maybe you would rather not deal with when it come to deployment (Keep in mind, you will most likely be deploying this application more than once unless somehow you get ir right on the first try with no bugs).

     

    There is a 3rd option availible to you out there.  That is the option of a SmartClient application using ClickOnce deployment.  This gives you the best of both worlds.  You get the ease of deployment by having to only deploy to a web server, but the richnes of a windows application. 

     

    Hope this information helps you out.

     

     

     

    Tuesday, March 4, 2008 11:59 PM

All replies

  • Hi,

     

    Welcome to the MSDN forums.

     

    If your application will be used by only a department and the department is connected using LAN, go in for a windows app. Some advantages of a windows app are rich UI, high performance and robustness, can use full-trust model etc.

     

    If your application will be used by the general public,i.e people outside the organisation or employees who want to access the app outside the office: go in for web application. Some advantages of a web app are wider audience, easy deployment. However you will have to deal with issues like cross-browser app, slower performance as compared to windows.

     

    http://dotnet.celeritas.com/Windows-or-Web-Application.html

     

     

    HTH,
    Suprotim Agarwal

    -----
    http://www.dotnetcurry.com
    http://www.sqlservercurry.com
    -----

    Tuesday, March 4, 2008 11:49 AM
  • Mohammad

     

    I would have to say that there is alot to consider here.  Some of the things to consider in your platform decesion should be but not limited to:

     

    • Bandwidth of user
    • Users expectation of rich application
    • Location of users
    • System requirements of the users

     

    Web applications have come along way in the past couple years, but they are no where as rich as a windows client.  Windows clients are nice, but provide you with a level of complexity that maybe you would rather not deal with when it come to deployment (Keep in mind, you will most likely be deploying this application more than once unless somehow you get ir right on the first try with no bugs).

     

    There is a 3rd option availible to you out there.  That is the option of a SmartClient application using ClickOnce deployment.  This gives you the best of both worlds.  You get the ease of deployment by having to only deploy to a web server, but the richnes of a windows application. 

     

    Hope this information helps you out.

     

     

     

    Tuesday, March 4, 2008 11:59 PM
  • I agree with what has been said but I would consider it as a slider between a pure HTML site to a pure Win client. There are *lots* of options in-between, and you don't have to pick only one. If you write your code correctly the choice of which client 'channel' to use can be delayed or even multiple channels implemented. E.g. you could have a very simple HTML channel and a Silverlight channel. Or maybe a simple HTML, pretty AJAX site and a WPF client that communicates with a web server. Or maybe a Office doc, etc, etc The combinations and reasons for selecting them are numerous, "horses for courses".

    Wednesday, March 5, 2008 12:27 AM