On Dec 9, 2011, at 11:37 AM, mkowalski wrote: > The guide itself > (http://code.google.com/mobile/ads/docs/android/fundamentals.html) mentions > that it works on 1.5 or later, but that I should compile against 3.2 (APIv13) > or later.
Oof. As a Java developer, this means that if you inadvertently use a type that doesn't exist in API level 3, the compiler won't warn you. And if you change your project settings to use the API level 3 android.jar, you'll no longer build because of AndroidManifest.xml errors. > Currently, my minSdkVersion is 8, but I do have my targetSdkVersion set to 13 > but the flags 'screenSize' and 'smallestScreenSize' don't work when I try to > add those to my AdActivity in my manifest. This fails because we aren't providing assemblies for API level 13 (Android v3.2). Try setting your TargetFrameworkVersion to Android v4.0 (API level 14), that should allow it to build. > This is probably something simple that I am missing, but how would I go about > compiling against 3.2 or greater yet still allow for it to run on 2.2 or > greater? Either "very carefully" or "you don't." The "very carefully" answer is as above: set your TargetFrameworkVersion to Android v4.0, which should allow the android:configChanges attribute to work. However, this is potentially fraught with peril [0], as some Android types and members have "moved" in a backward compatible, but not forward compatible, manner. You will need to test your code to ensure that it actually works on your target platforms. - Jon [0] http://lists.ximian.com/pipermail/monodroid/2011-November/007350.html _______________________________________________ Monodroid mailing list Monodroid@lists.ximian.com UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
