Get Silverlight and WPF controls that
share the same code-base...
...and create solutions that work in cross-platform scenarios.
SILVERLIGHT & WPF
Sharing is good, knowledge is power
When discussing any two frameworks, even those as closely linked as WPF and Silverlight, there will be obvious differences to take into account when developing. These differences can help to guide us towards solutions that work in a cross-platform scenario, like a strong Service Oriented Architecture (SOA), all while leveraging the distinct benefits of each platform in our architectural decisions.
Silverlight targets Windows and OSX via both browser and Out-of-Browser (OOB) modes, with limited access to system resources, whereas WPF specifically targets the Windows desktop and has full access to all system resources.
WPF utilizes ClickOnce to install on Windows Desktop machines while Silverlight installs via the plugin on both Windows and OSX machines. While WPF requires a larger install (minimum .NET Client Profile), Silverlight runs on a much more compact plugin model but requires the plugin to function.
Silverlight is not so much a subset of WPF, but rather a combination of core functionality found within WPF and the .NET framework that allows developers to create rich and robust applications with a much smaller overall footprint on the system. This makes Silverlight a more streamlined approach for some scenarios, but if your main target is the Windows Desktop environment then a WPF-based solution may be a better choice.
FIRST WIN with XAML
Shared API / Codebase
The first way a Telerik XAML developer benefits from the similarities between Silverlight and WPF is how our developers have architected the Telerik RadControls for Silverlight and WPF. We derive both suites from a shared codebase and a common project, meaning that the same features and functionality exist between controls that the suites share. This helps to significantly lower the learning curve when moving from one framework to another as well as facilities a quicker transition if you suddenly find the need to switch frameworks mid-project.
- Controls built from the same project, reducing the learning curve of moving from one framework to the next.
- Mirror API and functionality between WPF and Silverlight, so for example RadGridView works exactly the same regardless of which platform you compile against.
- Zero learning curve between two suites, meaning your investment in XAML today will pay off for all future projects tomorrow.
SECOND WIN with XAML
Style & Theming
Another obvious win for the Telerik XAML developer is that we have done a tremendous amount of research into the styling and theming of our controls, down to the simplest animation and transition that you see when using controls like RadComboBox or RadTileView. The end result are sleek, professional looking controls that support 9 themes out of the box.
Moving beyond the basic themes we also have the brand new Metro theme, allowing you to deliver applications today that focus on a streamlined display of content that is as easy to customize as it is to implement. This allows you to bring application development in both Silverlight and WPF to the next level, preparing you for the Metro style applications found in Windows 8