Should I use WPF or ASP.NET for my next web application development?

Question

We have a web application that was built using MySQL / PHP / Javascript + JQuery with server side HTML. The problem is that of the 10 software developers who work for the company, not one of them is a PHP expert (we are all .NET / C # developers). I need to make a recommendation to my management team about which technologies to use as a platform for the next generation of web application products.

I want to use the .NET / C # experience that the company has and otherwise creates, and therefore tend to recommend some Microsoft technologies. We don’t need a client plugin and we don’t need vibrant animations / multimedia, so I exclude Silverlight.

Is WPF ready for prime time? Is ASP.NET deprecated WPF? How to choose between these two technologies?

The big question, I know ... I can clarify it based on your comments, if necessary.

Thanks for taking the time.

Answer 1

Your settings use ASP.NET and ASP.NET MVC web forms. WPF does not play here, but for desktop applications. ASP.NET and WPF are completely unrelated.

In any case, you need to use ASP.NET.

Answer 2

Unlike Greg and Tyler answers, you can use WPF in the browser as a WPF XAML Browser Application . They have some limitations compared to regular WPF applications, so this may not be the right solution.

Regarding the use of ASP.NET or ASP.NET MVC, you need more information about what you want to do with your web application. If you go with one of them, you may also need to consider which javascript library you are going to use (if there is one, for example, jQuery is very popular).

Alternatively, depending on the complexity of the application or its user interface, you should not drop Silverlight simply based on the reason for the client-side plug-in. Silverlight greatly simplifies the development of complex applications, and ongoing maintenance is easier, so make a decision in the whole picture, and not just in its part.

Answer 3

I highly recommend .net MVC with a new viewer called razor. this allows you to nicely separate layers and you can use many front-end technologies, such as jQuery, without all the heavy controls that web forms bring to the table.

I see WPF as a flash, and sometimes this is the best way, but for most web applications, which I would say should be MVC. You can also easily find support for this, both for the entire application and for specific layers of the application.