Hi

On 2012.02.20 22:35, Jason Awbrey wrote:
build it using the Silverlight client profile and see what breaks - that will give you a pretty good idea of where the trouble spots will be
Only few things I'd like to add:

 * SL client profile would be even more strict MT and M4A are supersets
 * if You are VisualStudio centric, before moving to MacOS+MonoDevelop
   compile
   with eval version of M4A


On Mon, Feb 20, 2012 at 3:34 PM, jmb <[email protected] <mailto:[email protected]>> wrote:

    Any good references as to best to grab a bunch of previously C#
    targeted code
    built on the .NET Framework to re-target this for the Monotouch
    runtime for
    use in either the Android or Mac environments? Looking to quickly and
    efficiently weed out API dependencies that fall outside of the
    Monotouch API
    coverage.

 * define smallest subset for platforms to be targeted (for me it is
   still WP, for You it'll be MTch)
 * use source code sharing with linking (ProjectLinker tool)
 * create projects (DLL assembly pro platform)
 * define project links (all code will be in superset project present
   as link)
 * copy all code to smallest-common-subset (WP)
   this creates links in superset projects (let say desktop, sl,
   asp.net etc...)
 * use partial classes - put/extract platform dependent code in
   separate file in class
 * move code from step above to appropriate platform projects (they are
   something like deltas)
   Step ends up with (let say in a desktop DLL project):
     o common Class.cs file linked from smalles-subset project (WP or
       MT if You decide)
     o Class.Delta.cs file with platform specific code in platofrm DLLs
       (we use Class.WP7.cs, Class.MTch.cs and/or Class.M4A.cs)


    Any tips and/or suggestions much appreciated!

This way we retain our original code and project maintainable and just add MTch/M4A platform
specific stuff.
Linking of cs files does ProjectLinker...

We have managed to port LoB application with 40k lines of code in 2 man/days. Business Logic of course, Presentation Layer is WPF so we could not reuse a lot of XAML code... Target was M4A and I'm refactoring solution (naming, project organization, etc) to include
MTch in next weeks...

regards

mel




    --
    View this message in context:
    
http://monotouch.2284126.n4.nabble.com/C-Code-to-Monotouch-Target-tp4405196p4405196.html
    Sent from the MonoTouch mailing list archive at Nabble.com.
    _______________________________________________
    MonoTouch mailing list
    [email protected] <mailto:[email protected]>
    http://lists.ximian.com/mailman/listinfo/monotouch




_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch


--
Miljenko Cvjetko dipl.ing. ET
        Direktor/CEO
        Projektant rjes(enja/Solution Architect 
        Razvojni programer/Senior developer
        Voditelj projekta/Project Manager

IX juz(na obala 13
Kajzerica Zagreb
T: 385 1 7775555
M: 385 91 557 447 3
F: 385 1 7779556
e: [email protected]
w: http://www.holisticware.net

_______________________________________________
MonoTouch mailing list
[email protected]
http://lists.ximian.com/mailman/listinfo/monotouch

Reply via email to