Has microsoft abandoned Microsoft. Net? Where is the future of Net technology?-On the Microsoft technical line and. net technical line
Winform: The advantage is that it is easy to learn, but the disadvantage is that the interface is not easy to understand and the interface adaptability is poor.
Wpf: Microsoft integrated the graphic card rendering technology to introduce the interface design method. Imitating html and introducing its own xaml, winform can implement wpf, because wpf has a WindowsFormsHost control, it is prepared to host the winform control. For example, if wpf does not have a chart control, it can directly host a chart under winform. For example:
System. Windows. Forms. DataVisualization must be referenced.
<Window x:Class="WpfApplication1.MainWindow" xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:d="http://schemas.microsoft.com/expression/blend/2008" xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:FormChar="clr-namespace:System.Windows.Forms.Integration;assembly=WindowsFormsIntegration"xmlns:Char="clr-namespace:System.Windows.Forms.DataVisualization.Charting;assembly=System.Windows.Forms.DataVisualization" xmlns:WinFormHost="clr-namespace:System.Windows.Forms.Integration;assembly=WindowsFormsIntegration"xmlns:WinFormControls="clr-namespace:System.Windows.Forms;assembly=System.Windows.Forms" xmlns:local="clr-namespace:WpfApplication1" mc:Ignorable="d" Title="MainWindow" Height="350" Width="525"> <Grid Name="AAA"> <WindowsFormsHost x:Name="myFormsChart" FontSize="8"> <Char:Chart x:Name="chart1" > </Char:Chart> </WindowsFormsHost> </Grid></Window>
Wpf can make adaptive la S and make more dazzling animations. Therefore, wpf is worth learning and can completely replace winform. In fact, I have not touched winform for a long time. The conversion between winform and wpf is quite easy, because the. net Framework is the same and does not change much. The only obstacle is the xaml. However, wpf can also support controls for scheduling. What can be said?
Uwp: uwp is the evolution of wpf and also the degradation of wpf. Why? Let's talk about the advantages of uwp. The advantage of uwp is cross-platform (here the so-called platform is only Microsoft's own platform, wp and pc for win). This can be said to be an evolution, degradation means that many of the wpf functions are thrown away by uwp, And the compiled programs can only be released in the windows app store. That is to say, uwp is very closed. Wpf uses traditional methods.. net Framework. The exe program is developed, and uwp uses a new one.. net core framework, which is developed by appx. This appx can only run on win10 mobile phones and PCs.
Anyone familiar with. net knows about messagebox and openfiledialog. The new. net core framework uses openfilepicker and contentdialog in uwp to implement the same functions. Why does Microsoft do this ?! Because to adapt to mobile phones ,. net has never considered running on a mobile phone, So Microsoft has rewritten it. So if you are familiar with wpf and xaml, congratulations, you can easily create a uwp interface, but that's all, because you are familiar with many. net Framework has been replaced, as well as various permissions and screen adaptation issues.
In the past, I used to debug wpf with messagebox, and I was always honest and practical with uwp. writeline (), these are natural gaps that impede your transition from wpf to uwp, and there is also the highly criticized closed uwp issue. Compiled programs can only be submitted to the App Store for release, do you want to download qq for uwp from qq official website? Sorry, you need to jump to the Microsoft Store to download it. The software may be a little small, but considering the Wall Technology in China, the download speed of Microsoft stores has never been faster and is often paralyzed, the next big piece of software is dying!
The topic is back. Is the. net technology outdated? From the perspective of Microsoft's technical line, it is in progress. net and.. net core framework, from the current situation ,. net is better. net core, for the current windows desktop program ,. net capabilities. net core technology. So wpf is still the mainstream development direction of desktop program development in the future (the premise is to use the. net language), as for uwp? In my current opinion, it is only suitable for publishing small programs. When can Microsoft use uwp to publish its own vs and office suite and achieve the same functions!