Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m not familiar with WPF but I’ve seen things I like about it for web development.
I wonder which advantages has developing a WPFbrowser application over asp.net (webforms/MVC) and viceversa. are there things you can do or use in asp.net you can’t do in a WPFbroser application?
The difference is fundamental.
ASP.NET is pure web, with a Web Server where you have to host your code and the browser client where your html code generated by the server will work.
In case of WPF, is a stand alone binary that will be downloaded from the server and it will work with a plugin on some browser and it will run the application.
ASP.NET will do whatever a web application can do and on different browser / OS.
WPF will do almost anything you can do with a desktop (expect some limitation ex: printing that you can manage to activated if the user accept it) and it will work only in Windows that have the appropriate .Net framework installed in it.