Home > Uncategorized > Licensing Flex Data Visualization components on your build machine

Licensing Flex Data Visualization components on your build machine

November 12th, 2009

aka: Licensing the AdvancedDataGrid and Flex Chart components
aka: Getting rid of the Flex Data Visualization Trial watermark

If you want to set up an automated build machine to build your Flex projects, you’ll get the Flex Data Visualization Watermark on your AdvancedDataGrid and Chart components unless you properly license them. And no, you don’t have to install Flex Builder. (And it’s not license.properties! That was the first thing that came up in my Googling, but that was for Flex 2.)

Just find your flex-config.xml file, which will be in your SDK directory under “frameworks”. On my build machine, that is c:\FlexSDKs\3.3.0\frameworks\flex-config.xml

At the bottom you will want to add these lines:

<licenses>
<license>
<product>flexbuilder3</product>
<serial-number>1377-rest of your serial number here</serial-number>
</license>
</licenses>

I learned it all by reading this helpful post.

  1. January 27th, 2010 at 16:21 | #1

    I couldn’t get this to work. I am using fcsh and not FlexBuilder. Do I need to pass in anything to the compile line?

  2. February 25th, 2010 at 16:53 | #2

    Ralph, sorry for the late reply! I am not sure about the command line. It’s been a while since I built my build machine config, but at the very least, I would say that this approach hinges upon your command line build referencing the flex-config.xml in some way. In looking through my Ant build scripts, I see that I am passing the following parameter: -load-config=${flex.sdk.dir}/frameworks/flex-config.xml

    (which of course resolves to the full path to the config file)
    This is probably all no-brainer stuff, but it’s the best I got! Hope it helps.

  1. No trackbacks yet.