2

EDIT: To clarify, I am referring to the local database support: Local Database for Windows Phone 8 using Microsoft.Phone.Data.Linq namespace. I believe that the technology is based on SQL CE.

I have an existing Windows Phone 8 application that I would like to migrate to the new Universal Windows application framework. The application relies heavily on Linq to SQL that is baked into the Windows Phone Silverlight API. I understand that I can stick with Silverlight, but it seems to me that it is only a matter of time before Microsoft pushes us all to Universal. Additionally, it just makes sense if I want to present this application as a Windows application too.

So, I'm really struggling with how I could make this transition and not screw my existing users over. Clearly I could just rearchitect the application with a different data layer and let the users re-create their configuration, but that isn't a desireable way to treat my users.

I'm happy to migrate to a different persistence mechanism, but still the problem remains of how to get their existing configuration to migrate the data? The only option that I've come up with is to create an intermediate version using Silverlight that migrates the data to a new format, and then to later upgrade the application to universal. In this scenario it is still possible to lose users along the way if they miss the intermediate upgrade.

Ideas?

4

2 回答 2

1

执行迁移的 Silverlight 应用程序的中间版本是最好的方法。如果您在商店中有该版本一段时间，您应该让大多数用户过渡，尤其是在他们升级到默认情况下自动更新应用程序的 Windows Phone 8.1 后。

于 2014-05-22T14:15:41.483 回答
1

嗯...我不放心，但 Windows 8.1 的 SQL 已经可用，Windows Phone 8.1 的 SQL 处于预览状态。它不是 LinqToSQL，但它可以工作。因此，我认为，您可以尝试使用它与用户客户端上的当前数据文件进行交互，直到它们也是 SQL 数据库。试试这个：http ://blog.tpcware.com/2014/04/universal-app-with-sqlite-part-1/

于 2014-05-20T04:22:54.307 回答