Episode 021 – “More Mango Down Under” | Windows Developer Show

Episode 021 – “More Mango Down Under”

Download Episode

approval payday loans

Special Guests

Chris Walsh

Rafael Rivera

News

Microsoft Announces the RC of the SBS 2011 Essentials Windows Phone 7 Connector
Job Posting Hints at Major WP7 Updates Each Year
Microsoft to Offer Developer Devices With Mango Next Week
Riots, Fire, Destruction After Vancouver’s Loss
Introducing Mobile Test Drive

Developer Tip of the Week

Portable Class Library Project:

Special Announcement

ChevronWP7 Labs

4 Responses to Episode 021 – “More Mango Down Under”

  • Sheeds

    Downloading now…and linked at my Blog: http://bit.ly/lArs6D :D

    Reply
  • Thom

    Great episode as usual :) @theSwannStudios

    Reply
  • Kelps (Silverlight MVP)

    First of all, great podcast. Congrats guys.

    Here are some of my thoughts about some of the topics from this show:

    Dropbox vs Skydrive : I belive that there are 3 main reasons for Dropbox to be more popular than Skydrive. 1 – Public APIs. If Skydrive had public official APIs, having apps for iPhone, Android or even WP7 would be easy, as any developer would be able to create them. That’s why Dropbox got so popular so fast. 2 – File size limit. Why does Microsoft need to limit the file size to 50 Mb? I am a Skydrive user since the beggining and a Dropbox user for the last 4 months and I already use Dropbox more then Skydrive, just because of the file size limit. 3 – Too many Skydrives. Why is it that I have at least 3 different and isolated Skydrives, instead of 1? The Skydrive used by Live Mesh is not the same as the main 25 GB Skydrive, that is also not the same as the Skydrive account associated with my WP7. Why make it so difficult for the user? To me, they should simply unify all my Skydrive accounts into a single one with maybe 30 GB, make a public API available (over REST would be awesome) and either raise the file size limit of drop it all together. BTW, the Skydrive API should’ve came with the Wave 4 of Live Essentials (Messenger, Mail, … 2011) but it didn’t happen and there is no word on why is that.

    Now about the WP7 data encryption you talked so much. The WP7 file system is already encrypted. Without the phone password there is no way to access the data. For the phones that have SD card slots (the Focus, for example), if you swap the card, the old card becomes inrecoverable because the phone will bind itself with the new card and trash the encryption key that was used for the old card. There is no way around it and it is a strong encryption. Also, there is nothing stopping you from encrypting the files you store in IsolatedStorage. IsolatedStorage is just an abstraction over the file system so, I don’t see what the problem is here. In fact, if you create an app that stores any kind of user password on the device and don’t use some kind of encryption on it, your app won’t pass the Marketplace validation (I know of a few apps that failed certification because of that and were forced to encrypt that data to pass). Also, with the Mango update, one of the things we’ll get is the ability to use stronger passwords that can be enforced by enterprise policies, so the phone is getting even more secure.

    I don’t see how SQLCE is a substitute for a file system. One could use IsolatedStorage in every scenario you presented for the SQLCE need. In fact, Jeremy Likness created a really good object oriented database called Sterling DB for WP7 and the Desktop Silverlight that stores the data in IsolatedStorage. I understand that people are used to SQL and may prefer that, but I would only choose to use SQLCE over Sterling if I had a really big set of data.

    Keep the great work guys.

    Reply

Leave a Reply

Post Comment