I posted a similar question to this group recently. AndroidManifest.xml supports "minSdkVersion" and "targetSdkVersion" attributes. The target SDK version being higher than the min SDK is supposed to mean you can use features from higher SDK level, but have taken steps to insure you are backwards compatible back to the min SDK level.
My experience is the same as yours -- "Minimum Android to Target" does NOT set the minSdkVersion attribute. And to complicate matters even more, there is a "Target API level" setting under "Android Manifest". One person who responded to my thread said that "Minimum Android to Target" did set minSdkVersion for him. I think both the minSdkVersion and targetSdkVersion should be exposed via the GUI, on the same page. I'm not too picky about what to call the fields. I filed a bug report on the topic (ID = 6221). I am not sure I have figured out the bug reporting system, though, since I have never seen any acknowledgement that a report has been received. Darren On Wed, Jul 25, 2012 at 12:57 PM, Neal Culiner <[email protected]> wrote: > I’m implementing features in Android OS 4 but still supporting back to OS > 2.2. I have the <uses-sdk android:minSdkVersion="8" /> in my > AndroidManifest.xml and all seems fine so far. However, to get support for > the newer features, as you know, I had to set the Minimum Android to Target > to 4.0. I then saw that the package that was sent to my device and later > an emulator was a higher package version. This leads me to believe I > should use the max version in my project to code against and this will also > send the latest package to the device to use.**** > > ** ** > > With this being said, I suggest we adopt the same thing MonoTouch adopted > for the SDK version with the term “Default” which uses the latest available > API installed on the machine or you can set it to a lower version as > needed. This would ensure that we’re always pushing the latest package and > also ensuring compatibility with the latest OS version. I noticed I had a > few conflicts with “using” statements when switching to a later API that I > needed to use a fully qualified definition such as with clipboard > integration using Android.Text specifically. **** > > ** ** > > What do you all think? Should we adopt “Default” for this setting like in > MonoTouch?**** > > ** ** > > Neal Culiner**** > > NC Software, Inc.**** > > http://www.nc-software.com**** > > **** > > ** ** > > _______________________________________________ > Monodroid mailing list > [email protected] > > UNSUBSCRIBE INFORMATION: > http://lists.ximian.com/mailman/listinfo/monodroid > >
_______________________________________________ Monodroid mailing list [email protected] UNSUBSCRIBE INFORMATION: http://lists.ximian.com/mailman/listinfo/monodroid
