Cross-Training in Silverlight & Flex – Platform Overview

More Cross-Training in SIlverlight & Flex

Shout it

This is the second article in which I will compare the technical details between Silverlight and Flex. Before I jump into the nitty-gritty of the two, I thought I would give a general overview of the platforms that are Silverlight and Flex/Flash/Air. Understand these terms and the tools up front will make it much easier to cross-train on the two technologies.

The Silverlight Platform

Microsoft created Silverlight as a small platform for developing Rich Internet Applications (RIAs) on the desktop, browser and mobile phone. Although it was inspired by the .Net platform and the Windows Presentation Foundation (WPF), Silverlight stands alone. In other words, users do not need to download the entire .Net runtime to execute Silverlight applications. They only need the small (about 4 MB) Silverlight player. 

As Flex is a framework that sits on top of the Flash platform, Silverlight is both – a runtime and an SDK. Silverlight applications can be developed to run “out of browser” on the desktop (similar to Adobe Air) or in-browser (similar to Flash Player). When run out of the browser (OOB), the application has access to extra APIs for file access and other system-level functions. Silverlight is also the primary application development platform for the Windows Phone 7.

Developer Story

Much like Flex, Silverlight employs a declarative UI mechanism (XAML) for defining the view of an application. Unlike Flex, Silverlight developers have the choice of many languages to integrate in their “code-behind” such as C#, Visual Basic.Net, F#, IronRuby and IronPython. The majority of Silverlight developers use C#.


Most Silverlight applications are developed using a version of Visual Studio, which is an IDE similar to Flash Builder.  Visual Studio comes in many flavors. Visual Web Developer Express is free and great for getting started. Most likely, as you get more involved with Silverlight, you will need to migrate to a paid version (Professional, Premium, Ultimate or Test). Although highly recommended, you do not need to use Visual Studio to develop Silverlight applications – the free SDK and command-line compilers are enough to build applications with. The open-source MonoDevelop is also an option for developing Silverlight applications. It is worth noting that Visual Studio is only available for Windows. Mac developers have the tools to develop Silverlight applications using Eclipse but this rarely happens.

SDKs and Toolkits

Unlike Flex, the Silverlight SDK is not open-source but it is free. It includes the minimum tools necessary to build Silverlight applications. Very often, build servers and CI servers use the SDK alone, to avoid purchasing a license to Visual Studio on the server. Although the SDK is not open-source, the Silverlight Toolkit (produced by Microsoft) is. The Silverlight Toolkit is an optional set of libraries that includes many add-ons such as rich controls, extended skinning and an in-browser test suite (Silverlight Unit Tester).


Visual Studio has an integrated graphical designer, but it is limited. Most people use Expression Blend to design, style and skin the UI. Expression Blend supports the import of assets from Photoshop and Illustrator. Expression Blend works on existing Visual Studio projects in parallel. This aids in a very tight integration between the designer and the developer. Flex cannot support this workflow very well. Even with the new version of Catalyst, projects are exported between the designer and developer – as opposed to the parallel workflow that Blend enables. Expression Blend only works in Windows.

Operating System Support

Silverlight does not have the same operating system penetration as Flex/Flash. Microsoft has fully committed to Windows and OSX for the browser and OOB capabilities. Silverlight does not, however, work in Linux. A separate project, dubbed Moonlight, aims to run Silverlight applications in Linux. This project is headed by the Mono team and it is perpetually behind the latest release of the Silverlight platform. Silverlight also runs as the primary application platform for the Windows Phone 7 and is being developed for Symbian, but it does not run on Android, WebOS, or iOS at this time. (possibly, in the future?)

Getting Started

The easiest way to get started with Silverlight is at From there, you can download all of the tools necessary to write applications in SIlverlight (Visual Web Developer, Expression Blend trial, Silverlight toolkit, etc)


The Flex/Flash/Air Platform

In my opinion, the branding of Flex/Flash/Air can be confusing. I will attempt to make it simple. Flash is the platform.  Flex is the framework. Air is Flex/Flash on the desktop (and devices outside the browser). In other words, Flash is the platform we all know and love. It has existed for a long time (since at least 1996) and has a rich history. Flash, by itself, is not very good at writing Rich Internet Applications (RIAs) – it is very good at vector animation. Flex was introduced as an SDK to sit on top of Flash to enable application development. Air was introduced to allow Flex applications to run on the desktop.

If you were to compare the Adobe technology to Silverlight, Flex/Flash is to Silverlight as Air is to Silverlight Out-of-Browser.

Developer Story

Much like Silverlight, Flex employs a declarative UI mechanism (MXML) for defining the view of an application. Unlike Silverlight, Flex developers only have one language choice available to them – ActionScript. ActionScript is an ECMAScript-like language, similar to Javascript but with optional static typing, classes and interfaces. Developers can also enable legacy C and C++ code to run in the “ActionScript Virtual Machine” by using a currently in-development technology called Adobe Alchemy.


Developers tend to use Flash Builder as the IDE for producing Flex applications. Unfortunately, there are not any free versions of Flash Builder (there is a free 60 day trial). Flex developers also have the option to use IDEA Ultimate by JetBrains, which is also a paid product. Unlike SIlverlight, these IDEs work in WIndows, Mac or Linux. Like Silverlight, the SDK is free and does not require an IDE to develop with. Other options are FlashDevelop and Tofino – a Visual Studio plug-in for Flex development.

SDKs and Toolkits

The Silverlight SDK is not open source. The Flex SDK, however, is open source. It is a very simple zip-deployed download that can be copied anywhere you need. This makes integration with build and CI servers a cinch. By default, you use Ant for the build system, but any build manager. Similar to the Silverlight Toolkit, flexlib is a suite of value-added controls that you can bring into your solution.


Since Flex is an Adobe product, the primary design environment is Photoshop (raster art) and Illustrator (vector art). A third tool, Catalyst, is added as a bridge between the art tools and Flash Builder. Catalyst allows you to produce skins and styles using the Flex parts model. In the current release, the workflow is one way – Catalyst exports to a Flash Builder project. In future versions, Flash Builder will be capable of exporting back to Catalyst for a more bi-directional workflow. As far as I know, Catalyst does not support the parallel designer-developer workflow that Expression Blend does. 

Operating System Support

Flex has a rich set of operating system support. Flex already works in Flash (browser) on Windows, OSX, Linux and Android. In the near future, Air applications will also be deployable to iOS, Blackberry, Android, Windows Phone 7 and GoogleTV in addition to Windows, OSX and Linux. The list is so exhaustive, I am probably missing some. In future versions of Flex, Adobe has strategies for managing different form factors. Air 2.5 will include all of the APIs for mobile devices that you would expect (GPS, accelerometer, multi-touch, etc).

Getting Started

The easiest way to get started is to go to the Flex product site and download the 60 day Flash Builder demo. Adobe also has demos of Catalyst, Photoshop and Illustrator.

Tags: , , ,

4 Responses to “Cross-Training in Silverlight & Flex – Platform Overview”

  1. [...] Adventures in Ruby MVVM – Wrapping it up Cross-Training in Silverlight & Flex – Platform Overview [...]

  2. Cross-Training in Silverlight & Flex – Platform Overview…

    Thank you for submitting this cool story – Trackback from DotNetShoutout…

  3. [...] This post was mentioned on Twitter by Dianne Marsh, Brian Genisio. Brian Genisio said: Blogged: Cross-Training in #Silverlight & #Flex — Platform Overview — #fb [...]

  1. I love this series already Brian – seriously. Great to read your thoughts from the other side (let’s call it the Dark side for now :).

    Two extra points I might have added here are the choice of server side platforms and typical developer frameworks.

    On the former, obviously Flex errs towards Java – with BlazeDS and LCDS supported by Adobe. Although I personally have used AMF extensively with .NET (via WebORB and FluorineFx) – which is a nice way of sharing remote objects between Flex and .NET. Obviously Silverlight can be hosted on Apache, but what about communicating directly with Java or PHP on the backend?

    As to the latter, there is obv a lot more discussion within Flex on micro-architectures – Cairngorm, Parsley, PureMVC, Mate, Swiz, et al – than in Silverlight. I personally believe this is due to the flexibility of the Flex data-binding system (which also tends to be misused due to all the codegen done in the compiler behind the scenes). Silverlight (and WPF for that matter) seems to focus purely on the MVVM and MVP patterns without requiring external plugins – though I believe that is partly due to .NET devs strong preference on MS-provided solutions first and foremost. That said, how pervasive is Prism in Silverlight these days?

    I know you’re planning to cover each with separate articles, and I look forward to each of these.


Leave a Reply