Flex Best Practices - Multiple Flex Projects or 1 Project, multiple Application MXML files

Question

Having seen several different ways of setting up larger projects in flex, I'm wondering what your opinions are of how to organize projects that are going to require 2 or more different applications. For example a public and private site within the project.

The two main ways that I know of would be first, creating one flex project, and then adding different mxml application files. Both applications would be able to share code.

The other way (which I currently like, but have no way of justifying), would be to create a different flex project for each application, and any code that needs to be shared could be part of a shared flex library. I guess something about the separation of the applications I like more, especially since I'm either working on one or the other at a time.

What are your opinions, and do you have any reasons for doing it one way or the other?

Answer 1

I recommend the library approach. That said, you can still use multiple applications in one workspace (and I do), but it's handy to keep the "one project, one application" rule. My workspace might have 5 projects, each of which has an MXML application, and 4 library projects, which have none.