Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is a very general question, but here are a few resources that may help you get started:</p> <ol> <li>Video: <a href="http://www.youtube.com/watch?v=WkNbRUqnSSc" rel="noreferrer">Cross-platform Mobile Development</a></li> <li>Blog Post: <a href="http://www.gregshackles.com/2010/12/shared-libraries-for-windows-phone-7-monodroid-and-beyond/" rel="noreferrer">Shared Libraries For Windows Phone 7, MonoDroid and Beyond</a></li> <li>Book: <a href="http://shop.oreilly.com/product/0636920024002.do" rel="noreferrer">Mobile Development with C#</a></li> <li>Blog Post: <a href="http://blog.xamarin.com/2012/02/24/mwc_2012/" rel="noreferrer">Xamarin Mobile World Congress 2012 Unofficial Conference App Released!</a></li> </ol> <p><strong>Edit (to answer your new questions)</strong></p> <ol start="5"> <li><p>The idea behind linking files across projects is that there is only one actual copy of the file, rather than having to manage multiple copies and keep them in sync yourself. The file will actually exist in just one project and be linked into the others, but when the projects are compiled it treats the file as if it were actually there.</p></li> <li><p>I can't speak to exactly how they created their folder structure, but I know there have been many cases where I would manually edit project or solution files to get the folder structure I want, because there was no way to get what I wanted through the IDE alone. This really boils down to personal preference on how you want your folders to be structured.</p></li> <li><p>In the end, what you need is a class library project for every platform you want to target. When going with the linked file approach, it's totally up to you where you put the physical files. One approach I use often is to actually create a standard .NET 4.0 class library, put the files in there, and then link them into my Mono for Android and MonoTouch class libraries. If all you care about is targeting iOS and Android, that may be more trouble than it's worth, and you can just let the files live in one project and link them into the other.</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload