WinForms Vs WebForms

WinForms Vs WebForms

• Joe Szymanski

  swamyk,
  
  these are two different animals; completely different ballparks...
  
  winforms are for windows client apps.
  
  webforms are for web applications that are delivered using http and that are rendered inside the browser.
  
  WM_FYI
  thomas woelfer
  
  

• Ares01

  generally speaking WinForms are Richable but not reachable , on the contrary WebForms are Reachable (but not richable due to performance factors).
  so the question is : can we have a form that is both richable and reachable at the same time . the answer is simply , yes "Click-Once deployment ".
  there was an old article about hosting a windows form over IIS , and this would lead to the death of browsers we know today . http://msdn.microsoft.com/library/default.asp url=/library/en-us/dnadvnet/html/vbnet10142001.asp
  so if we can really work this way by hosting winforms over IIS , why would we need webforms at all
  i first heard this idea by Chris Sells on his wonderful Guerill.NET in london , he really convinced all the audience that time that browsers are really going to vanish.
  so the
  
  but if you need just a comparison that would be on a very huge list of faactors :
  for example :
  1- Security ( Role based and CAS in win vs only role based in web)
  2- graphics (GDI+ in win)
  3- Resposiveness ( very quick in win)
  4- Framework ( windows forms require .NET fx)
  5- programming model ( win32 msg pump in win vs HTTP model in web)
  
  there is another factor which will forever still a difference between win and web , which is state management . windows develoepers dont have to take care of state management they save their state in variable , but web develoeprs need a mechanism for state mgmt of course .
  
  i hope this help

  
  

• Tom Albrecht

  Depends on your user base, intranet based acces winforms are great and for internet access with passport authentication webapps are a must.
  
  

• Josh Pendergrass

  Thanks for the information
  
  

• krissmith

  Yah they are completely different beasts. Is there any particular/specific piece that you are looking at comparing
  
  Generally speaking (very general). If you require a very powerfull, feature rich, user interface you will spend much less effort developing it in Winforms. Additionally you can get some of the deployment benifits and some offline capability if you implement some Smart Client features.
  
  If you have no control over your client (eg you can't get .Net framework installed due to limitations such as control or OS) then ASP.NET is a good choice.
  
  Once again this is very generic advice for a generic question
  
  Regards,
  
  Josh Carlisle
  
  

• ez.xcess

  • Winform not require hosting on server while Webform required hosting on server.
  • Winform is faster performance than Webform.

   

  
  

• ND..

  Wait till Xaml comes along and we can have the best of both world's.
  
  From my experience when I am working with data heavy applications I like web forms. Why do i like web forms for data because it is alot easier to display data in a million ways with HTML then it is with Windows Forms.
  
  Obtaining a rich client experience however is alot more difficult in Web Forms. Often times these situations are best suited for Applications. 
  
  There is also the No Touch .NET Applications which allow you to host/launch .NET based Windows Form applications in a underprivielged environment. This has the bonus of allowing users to be able to run rich client applications in an environment where they normally would have to use a web page. Extremely useful for intranet sites where you have a specific policy/guideline. Not very reliable in the real world, however.
  
  When deciding what you want to you use, you should carefully analyze which you know best and who your end user is going to be. In many cases a Web form solution will not fit a Windows form solution based on criteria such as , platform, deployability, security and etc.
  

  
  

• ramuty

  WebForms have HTML at their back or the base is HTML whereas WinForms does notm have HTNL embedded in them. Moreover, WebForms need web browser to be viewed but WinForms dont need them.
  
  
• WinForms Vs WebForms