use one solution for each app. Break your app up into logical components (UI, db access, etc) and put each component into it's own project
a solution is basically just a collection of projects, so each app's solution could reference projects that are used in other apps also (ie, common db functions) On Wed, Sep 28, 2011 at 2:46 PM, Van Swofford <[email protected]> wrote: > I’m starting to build a MonoTouch / iOS commercial app. Some of the > assemblies will also be shared with in-house Mac console apps, eg. the > assembly with the database classes will be used on the iPad to extract data, > and also by the in-house app to build the database that’s distributed to the > customers.**** > > ** ** > > How best to organize the solution? Should there be a single solution with > projects for the various components (main iPad app, assemblies, in-house Mac > console apps, etc.)? Or should there be a solution for each application > and/or assembly?**** > > ** ** > > I’m coming from a Delphi background, and new to .NET, so the basics of > solution organization are new to me.**** > > ** ** > > Thanks!**** > > Van Swofford**** > > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch > >
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
