Continuous Build: Flex vs Sliverlight

It’s hard not to continue the recent “vs” style postings given the pain I incurred with Flex Builder 3. The problem should have been fairly simple, generate an Ant script so I can plug a Flex project into a continuous build environment. If I’d be using Silverlight life would have been pretty simply since Visual Studio uses MSBuild, so I basically have to do nothing other than point the continuous build process at the MSBuild script and inform it about the source control system I’m using. Easy!

In Flex land, things are a little different . Reading Adobe’s Ant Task page you’d expect things to be fairly simple. Unfortunately the Ant Tasks page isn’t very specific about how to pass in library references for , luckily you can guess the answer from this blog – compiler.library-path. include-classes is another headache that Straylink offers a solution. index.template.html is again poorly documented by Adobe, but Renaun Erickson’s posting together with Mike Morearty who nicely documents the marco’s. If you’ve got this far, you need to consider added your FlexUnit’s to Ant.

If you got past all the above, you should read Daniel R.’s blog and PowerPoint, realize you have wasted the last time period on Adobe’s madness, and download Antennae.

The above is painful. Adobe may have 98% of internet viewers today but its Flex Builder needs a lot more work, as does its documentation.

Update: If your using FlexMdi and don’t see the correct images for close, minimize etc, then read this, comment in this and this.

Update: Why does Cairngorm FrontController base class mandates a 1:1 coupling between a particular event and a command class?

~ by mdavey on January 3, 2008.