Silverlight / WPF Programming with Windows Forms Skills

To what extent can there be one Silverlight / WPF program with Windows Forms skills?

To what extent is this normal for internal developer applications in a style similar to Windows Forms?


The background for my question is what I am applying to positions where Silverlight is required, and I am trying to argue that my experience with Windows Forms should be sufficient for internal applications.

I know that Silverlight / WPF offers a lot more, but mainly for “fancy” things on the network, as is the case with higher SoC through the MVVM pattern.

+3
source share
5 answers

, WPF/SL, WinForms , , .

, , WPF, WinForms ( ), , WPF WinForms, WPF, , ; .

WPF/SL ( , ), WPF/SL (XAML, Binding, Commands, DependencyProperty, Styles, Triggers ..), , (, /).

, , ( WPF) WinForms, , ..

+3

, - , WPF, WinForms, , , . , - , WPF, " " " -".

, : " , , , , , ".

+3

, WinForms, SL/WPF; , , SL/WPF XAML, .

" 10 , Silverlight WPF" . Silverlight 4 , .

+2

, , Silverlight/WPF. , , , , , , XAML, Winforms, . , , , WPF/Silverlight: , , , .. , , .

, Winforms . - , , , , , , , . , , Silverlight WPF - , , .

, , . , , - WPF-, , , , Winforms, , .

, Winforms " " , Silverlight/WPF, , ++ " ", # . , , , , . , - , , - - .

+1

Inevitably, your first wpf application will look like a winforms application. As far as I know, this is normal. But there are people who will kill you if they find that you made 30 conversational applications without using MVVM :)
Anyway ... you have your first WPF project to be completed ... you will probably end up are going to encode how its winforms (code behind heavy).

0
source

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


All Articles