4 Replies Latest reply: Jul 1, 2011 11:26 AM by gshokie02 RSS

    Updated workspaces for FB4.5?

    gshokie02

      Can you update the links for the provided FlashBuilder workspaces so they are compatible with FlashBuilder 4.5 out of the box?  When opening them, I get a warning message saying they were created for an older version of FlashBuilder and I should export/import all projects to update them.  Will this be a problem with my own projects as new versions of FlashBuilder are released or is there an auto-upgrade option planned?

        • 1. Re: Updated workspaces for FB4.5?
          Flex in a Week, FiaW Community Member

          Are you talking about a particular link within an exercise?  Can you be more specific?

          • 2. Re: Updated workspaces for FB4.5?
            gshokie02 Community Member

            So far, all of them.  I got the error first when I downloaded the Day 1 workspace and now again with Day 2.  I'm using FlashBuilder 4.5.1 Premium on OS X, JDK 1.6 update 24.

             

            Error Message:

            Workspace Error.png

            • 3. Re: Updated workspaces for FB4.5?
              gsc811

              I believe what gshokie02 is referring to is the fact that the version 4.5 exercise files are recognized as previous version content once the 4.5.1 upgrade is installed. The program warns against using these files as they might cause corruption of the project (or possibly the software itself).

               

              As Flash Builder evolves it would be logical for Flash Builder to not just notify of previous version content but offer a built in option to update not only the current project file, but perhaps also to be able to choose a folder and auto update/convert all files within as necessary.

               

              I hope this helps clarify things.

               

              gsc

              • 4. Re: Updated workspaces for FB4.5?
                gshokie02 Community Member

                Exactly what I'm talking about.  NetBeans, for example, offers this functionality with its upgrades -- when you open a 6.8 project in 6.9 it prompts you that it will upgrade it to the new format and you may or may not be able to open it in the older version (depending on the changes).  Having to export from the old version, then re-import to the new version seems like a lot of effort that I should only have to take if I decline the automatic upgrade.