I'd suggest creating three projects, one for Flex, one for Air, and one Shared. Flex and Air project can reference Shared (either as a library or as a source path). That will also help prevent accidentally referencing Flex/Air specific code from something that's supposed to be Shared.
HTH, Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building Flex based products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -----Original Message----- From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Dennis van Nooij Sent: Monday, October 22, 2007 10:21 AM To: [email protected] Subject: [flexcoders] Share Code for Flex and Air projects Hi, Our project here has to run on both the web and in Air and I'm looking for a solution how to structure my project. Lots of articles about how to convert a Flex project to Air, but it's all "no way back". I found this link http://www.simplifiedchaos.com/2007/08/09/how-to-compile-both-flex-and-air-a pplication-from-the-same-codebase/ buth as the author says it has some issues (next to the listed ones you can't use mxml for the parent views). Is there anyone who uses a different approach ? thanx, Dennis
