Thanks to all for the replies. I can rest in peace with multiple assemblies and not worry over impacting load times.
Cheers, Greg On 08/07/2012, at 4:35 PM, rnendel11 wrote: > When I first started using MT I stressed on this quite a bit - coming from > the windows world and watching "any cpu" applications take *forever* to > compile. However, I just posted a "significantly" large application that > references 6 different custom class library assemblies, many other > assemblies, and copies a default DB on first load, all in under 6-7 seconds > (at most) on an actual device. Load time really isn't too much of a concern > as far as I can tell. If Apple says otherwise over the next few days, I'll > certainly post here :-) > > FYI - this app uses networking (tcp/ip stack), copies a default DB, links to > 6 custom class libraries common to windows/android/IOS, etc... and loads on > first initialization well under what I had feared so long ago - IMHO, do > what "best practices" tell you and, in the end - on a physical device - you > will find acceptable performance and load times. > > -- > View this message in context: > http://monotouch.2284126.n4.nabble.com/Impact-on-load-time-with-many-assemblies-tp4655805p4655845.html > Sent from the MonoTouch mailing list archive at Nabble.com. > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch _______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
