Shulou(Shulou.com)06/02 Report--

Editor to share with you what is the key difference between WPF and Silverlight, I believe that most people do not understand, so share this article for your reference, I hope you can learn a lot after reading this article, let's go to know it!

When Silverlight was born, many people simply understood it as a competitor to Flash. However, with the further work of Microsoft, Silverlight is used more and more widely, and many people even confuse it with WPF.

As WPF and Silverlight become more and more valued by .NET developers, the line between them becomes more and more blurred. Back in June, Wintellect released the little-known but extremely important White Paper on the similarities and differences between Microsoft WPF and Silverlight. We recommend that GUI developers read through all 69 pages, and we will list the main ideas and their impact on relevant business scope developers.

Dependency attributes are an important part of the two platforms, and PropertyMetadata can be used instead of normal fields to save properties. Silverlight provides only this class, while WPF has several subtypes available.

UIPropertyMetadata added an identifier to determine "whether the animation of dependency attributes should be banned where metadata instances are used"

FrameworkPropertyMetadata adds an identifier to indicate which attributes affect the pipeline, including control management, measurement, and rendering. It can also be used to indicate whether the property allows data binding and the default type. Because Silverlight does not support this class, all data bindings are one-way by default.

Silverlight does not support tunnel events. Both platforms support Direct events and Bubbling events.

WPF supports multiple types of triggers. When a simple trigger is attached to a dependency property, the style is automatically modified when the trigger condition is met. In addition to simple triggers, WPF also supports triggers that respond to routed events or use data binding.

Silverlight uses the visual state manager instead of triggers. This technology is not currently available in WPF, but will be added in WPF 4.0.

Silverlight only supports several tag extensions. In addition to the general StaticResource, Binding, and TemplateBinding extensions, WPF adds DynamicResource, RelativeSource, x:Type, x:Static, and x:Array.

There are many keyboard and mouse events available only in WPF. Due to a large number of relationships, we will make a complete list later.

About UIElement classes and IInputElement interfaces. When a control is disabled, WPF uses them to disable all child controls. Silverlight does not provide this functionality, so developers have to traverse the control tree manually.

Silverlight is limited to BasicHttpBinding and PollingDuplexHttpBinding in terms of communication. Of course, WPF supports all bindings.

The printing function is also completely different between the two. WPF can print visual trees directly, while Silverlight relies on browsers.

The above is all the content of the article "what is the key difference between WPF and Silverlight". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.