Silverlight Vs. WPF Vs. Winforms What is good for my purpose?

I am going to launch new Windows applications, and the rivals for the platform are:

  • Windows forms
  • WPF
  • Silverlight

Now my experience with WPF, at least in my last application, was not very encouraging (the application did not start on the deployment machines, and I had to do it again in Winforms). So my confidence is shaken here.

My application is intended for mass distribution (the latest version contains 100,000+ installations). Therefore, I want to be absolutely sure that my users can use it and enjoy it without any problems.

I would like to create a nice interface by moving on to the next step as a Flex or Silverlight application, an iPhone with animations and effects. So I would really like to go with WPF or Silverlight if I can.

My needs

  • Good support for visual effects and animation effects.
  • Support connect to database.
  • Print support (is there an equivalent to PrintDocument in Silverlight)
  • You cannot suffer from deployment problems.

Silverlight is universal, but does it have print support and a set of tools for good management? WPF has print support and a good set of tools, but can I depend on this? Winforms is dated already and not so impressive, but should I go with it anyway?

Your advice will be appreciated.

+4
source share
4 answers

Good support for visual effects and animation effects.

So these are really WinForms if you don't want to do something in a painful way.

Support connect to database.

WinForms and WPF can do this directly, Silverlight needs support from the backend server (although it may be SQL Server, which provides data as a web service).

Print support (is there an equivalent to PrintDocument in Silverlight)

Silverlight 4 has good print support, if you plan on targeting Silverlight, you will be targeting SL4.

You cannot suffer from deployment problems.

All technologies suffer from deployment problems. His question is about the nature and extent of these problems.

Silverlight has the advantage that the client does not have a complete .NET platform and runs on a Mac. You will need to deploy through a web server.

+4
source

First, the deployment problem is not your problem. If you ask the client to do something, you offer technology, they check, and that is their responsibility. I am currently involved in software at the bank, and we are VERY limited, but this is not my problem: I know what I can use, and I can ask administrators before going on unsupported paths.

It says - check before asking what YOU WANT or CAN support.

I would go for WPF on .NET 4.0 these days. I really do for a complicated trading application. Together with a web application for the administrative side (quite a lot, and I use a dynamic data infrastructure there to add users, etc. Simple in code).

After that, I would try Silverlight. Especially 4.0 - the new "local mode" is excellent, install it locally, even with a shortcut in the menu. There is no real difference with the user, and XAML on Silverlight 4 is much better than the earleir version.

I would try to stay away from Winforms - it is much less flexible.

But in the end you must first check the requirements. For example, here, where I am currently working, .NET 4.0 is “no,” and Silverlight in ANY version is “no,” until they are updated on a standard system image.

+2
source

It all comes down to how much time you have.

If you have a short time, it is best to go with what you know (WinForms), but if you have a lot of time to develop it, it may well be worth spending on Wpf, since animations and visual effects load better instead of WinForms.

  • Animations and visuals easier / better in WPF
  • Both have connectivitiy database support (.NET supports wpf and Winforms).
  • Printing is also not too complicated.
  • WinForms can focus on .NET 2.0, which makes deployment easier. Wpf should target 3.5, which means your users should use the latest version. Also, if you are developing .NET 3.5 SP1, you may run into problems with users who do not use SP1. This can lead to deployment problems and usability.
+1
source

If you are willing to pay, then go to the Telerik Win management form and Silverlight 3 supports printing .

0
source

Source: https://habr.com/ru/post/1304751/


All Articles