Posted by jason on Mar 15, 2010 in
iPhone If you are using the iPhone simulator to test your web application, you can query sqlite3 cache tables by going to the following directory:
~/Library/Application Support/iPhone Simulator/User/Library/Caches/com.apple.WebAppCache
Command to open the cache database:
sqlite3 ApplicationCache.db
Once inside, you can use the following command to view the tables:
sqlite> .tables
This is very helpful in troubleshooting caching issues.
Posted by jason on Mar 2, 2010 in
Windows Mobile Previously, I wrote about signing cab files for Windows Mobile 6. The application was initially created for Windows Mobile 5 Pocket PC devices. We got it working on Windows Mobile 6 Pocket PC.
Recently, I was tasked with creating an installer application to get around some of the browser inconsistencies they’ve been experiencing with the various Smart Phones. They have an installer app that has an executable and an XML file that the executable reads for it’s configuration. Pocket PC allows you to download the XML file and the executable file and everything just worked. The Smart Phones do not behave this way. I created an app that downloads both the EXE and the XML file to the My Documents directory and launches the EXE. Works great.
My problems started when I tried to cab up the whole thing and install it from a mobile device. I signed each file inside the cab as well as the cab itself. I kept getting prompted by the device asking me if I want to trust this unknown publisher? At first, I thought maybe I had screwed up the signing. Turns out that no, I did sign it correctly… for windows clients. The Windows Mobile platform uses a different technology than Authenticode.
On this MSDN article about how to Sign your Windows Mobile Application, it states very clearly: ”Authenticode signatures for other Windows platforms, such as Windows Client or Windows Server, use a different technology than Windows Mobile code signing and are not recognized as valid normal or privileged mode signatures.” What I don’t yet understand is that it states Windows Mobile (not Smart Phone) uses a different technology, yet we used Authenticode to make the prompts go away for the Pocket PCs we were testing on (Windows Mobile 5 and 6).
The Windows Mobile code signing seems very expensive. From what I can tell it costs $350 for 10 signings. There is an additional fee for each signing after that. What this means is that you better be darn sure your application is finished before signing your application. I’ve read that you have to submit your signed cab to Verisign who then signs your cab file with their certificate. I am beginning to hate the Windows Mobile platform and might actively root for their demise…