Building rich ASP.Net client is often more complex than building rich Win
apps.
Do not forget that a windows app should act as a client of a web service, or
a wcf service (if you use .Net 3.0).
If you build your application in a SOA fashion, you can even have a full
rich windows APP that is a client of a service somewhere on a server, or a
"less" rich web application for users that does not have the windows app
installed.
Concerning the managability, a lot of developpers say a windows app is a bit
more difficult to maintain because of deployment scenario. They are right,
but some home made updater or clickonce technologies can override this
limitation... you can ensure the client app is running the correct version.
Finally, the scalability is easier to raise with a windows app if it uses
the disconnect mode (using local cache - datasets - to work and send updates
to the server when it is finished), in opposition to a web application that
will continously serve pages to users (that should ponderated snce, ASP.net
can serve a huge number of pages on small servers...)...
To resume, you have to deal with the pro and cons of each technologies...
there is not yet an "ultimate" way to do your app.
Steve
"tom c" <to******@gmail.coma écrit dans le message de news:
11**********************@b28g2000cwb.googlegroups. com...
What are the reasons you would decide to do a dot net app in the
Windows desk top mode, rather than in ASP.Net? I am being asked to
make a recomendation and I can not think of any reason to go with desk
top, even for something that is only going to run on one desk top
computer at a time.
My thinking is that with Win XP you can always use IIS and run the app
on your desktop. If you ever need to migrate to a web app it will be
so much easier if you start out with ASP.Net, and in dot net it doesn't
take any longer to develop in ASP.Net.
So those are my thoughts but I am not an experience dot net developer,
so tell me what I am missing.
