I put all the common code in one assembly, and then had 2 main assemblies (seperate solutions in my case), which used that common assembly. Worked well.
On Mon, Jun 4, 2012 at 1:16 PM, David Junod <[email protected]> wrote: > Ended up creating separate directories for each exe with its own project and > then soft linking to the src and images directories of the base. > > On Jun 4, 2012, at 4:11 AM, David Junod wrote: > >> I have a single set of source files. >> >> I want to build two slightly different executables. >> >> One named appSingle and the other named appMulti. >> >> When building appSingle, I will define SINGLE and have some #if SINGLE code. >> >> When building appMulti, I will define MULTI and have some #if MULTI code. >> >> The problem is in the Info.plist. >> >> How do I manage that? MonoTouch insists on it being called Info.plist >> >> _______________________________________________ >> MonoTouch mailing list >> [email protected] >> http://lists.ximian.com/mailman/listinfo/monotouch > > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch -- Nic Wise t. +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise b. http://www.fastchicken.co.nz/ Earnest: Self-employed? Track your business expenses and income. http://earnestapp.com Nearest Bus: find when the next bus is coming to your stop. http://goo.gl/Vcz1p mobileAgent (for FreeAgent): get your accounts in your pocket. http://goo.gl/IuBU Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2 _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
