Flex Tip 4: Export Release Build (Flex Builder 3)

January 23, 2008 – 12:16 pm

If you are creating new project in Flex Builder 3 you will notice that there is no “bin” folder where the .swf, .html and .js files are stored. Instead you get a “bin-debug” folder with the files. This is because Flex Builder 3 threats the project by default as a debug one, running the .swf from “bin-debug” folder.

When moving a project from Flex Builder 2 to Flex Builder 3 you will get a strange feeling that the size of the .swf for the application gets larger in FB3 that in FB2. Its just a feeling, what FB is doing is compiling the debug version any time you Run or Debug the project.

To obtain the non-debug version of your application (also knows as release version) you will have to go to Project / Export Release Build. In the popup the “Export to Folder” input is already filled up with “bin-release”, thats where the release version of your project will end up after clicking Finish.

If you compare the size of both .swf from “bin-debug” and “bin-release” you will see the difference. The one from “bin-release” is the one that should be uploaded to the site or wherever you need it.

Another small and helpful tip for day-to-day work with Flex.

  1. 2 Responses to “Flex Tip 4: Export Release Build (Flex Builder 3)”

  2. I have a problem with Flex3 with FlexFM (Filemaker). When I build the export release there are no errors or warnings. And when I check the application (test.html/test.swf) in the bin-debug path - the application works correctly. But when I copy the path bin-debug (perhaps to c:/bin-debug), the connection to FileMaker doesn`t work.
    I can`t move the Export Release to the Server…

    Can you help me - do you know such problem?

    By gerd on Apr 18, 2008

  3. Hi gerd,

    Haven’t played with FileMaker but from what i’ve read seems that it’s embedded with a web server (IIS for Windows or Apache for Mac). Being that way i suspect that if you don’t manually set the connection endpoint in Flex, your client wont be able to run elsewhere than inside the server.
    For example, when using LCDS (LiveCycle Data Services) with a project build with LCDS wizard in Flex Builder, your client wont run elsewhere than on the server (JBoss, Tomcat or some other). If you copy the client files outside the server it wont work and probably you will get an error because the client will try to load http://localhost/crossdomain.xml wich is unaccessible outside the local server.

    I suspect its the same issue with the FileMaker, try to locate the server root folder and copy the client files and then access the client HTML file using http://localhost:SERVER_PORT/PATH_TO_HTML.

    BTW: what server-side technology are you using with FlexFM when building services that client connects for ?

    By Adrian Aioanei on Apr 18, 2008

Post a Comment

site map