Jon Westfall
05-31-2007, 04:25 PM
<div class='os_post_top_link'><a href='http://blogs.msdn.com/windowsmobile/archive/2007/05/30/all-about-application-locked.aspx' target='_blank'>http://blogs.msdn.com/windowsmobile...ion-locked.aspx</a><br /><br /></div><i>"Some non-touchscreen Windows Mobile devices ship with a set of security policies that prevents developers from adding their own codesigning certificates. I don't know of any touchscreen devices that ship like that - it's possible to configure those devices to be locked down but none ship like that by default as far as I know. For some of these devices, it's possible to tweak the security policies via supported methods so you can install development certs,debug, and develop privileged applications. Internally we call this "the user is manager" meaning that the user has the ability to freely modify any software setting on the phone. In this post I'll describe how to figure out the security policies on your device and how to figure out if you are "application locked" or not."</i><br /><br />One of those wonderful features of non-touchscreen windows mobile devices (Remember, we used to call those "Smartphones") is the ability for OEMs to really lock down the phone from outside software vendors. This Windows Moble Team Blog post talks a bit about this locking system and how Developers can deal with it in their own applications.