Rich Client vs. Thin Client
-
Hello All, Does anyone have a link to the advantages/disadvanteges of Windows Forms vs. Web Forms in .NET? We operate a closed system that we're converting from VB6 and VC++ to .NET. Most everyone here is anxious to convert the UIs to WebForms. I don't see the advantege given we don't deploy over the internet. :sigh: Any thoughts?
-
Hello All, Does anyone have a link to the advantages/disadvanteges of Windows Forms vs. Web Forms in .NET? We operate a closed system that we're converting from VB6 and VC++ to .NET. Most everyone here is anxious to convert the UIs to WebForms. I don't see the advantege given we don't deploy over the internet. :sigh: Any thoughts?
Hi Don, IMHO, this question is quite broad to answer in a single post in the forum, may I suggest you to read the article Choosing the Right Presentation Layer Architecture[^] written by David Hill that might give you some ideas on this issue. You may also find some good info from the .Net Architecture Center[^]
-
Hello All, Does anyone have a link to the advantages/disadvanteges of Windows Forms vs. Web Forms in .NET? We operate a closed system that we're converting from VB6 and VC++ to .NET. Most everyone here is anxious to convert the UIs to WebForms. I don't see the advantege given we don't deploy over the internet. :sigh: Any thoughts?
Don Burton wrote: Most everyone here is anxious to convert the UIs to WebForms. Just do it! :) It's a worthwhile experience to learn ASP.NET development. Windows Apps + Rich controls for the UI + Usually better performance since all processing is done locally - Requires deployment and configuration of binary files on every client - Upgrades require deployment and configuration to every client - Connectivity to remote data sources may be difficult when running outside the intranet. Web Apps + No client deployment necessary; all they need is a link + Upgrades are a breeze since they're done to a central server + Access to data sources is available as long as access to site is available - UI controls are typically limited to the HTML ones - Most of the logic sits on the server so a network round-trip is usually required, hindering performance - Performance tends to degrade as more clients use the site simultaneously So it boils down to this, a web app incurs very little upfront costs in terms of deployment and upgrades, but the UI experience tends to suffer in terms of richness and performance. A Windows app is pretty much the opposite. However, if higher performance is needed for a web app, you can always add faster and/or extra servers and all clients benefit immediately. With a Windows app you need to update all the client machines and/or spend time deploying a faster version of the app. Regards, Alvaro
