唯一地标识在Windows话机通讯录 [英] Uniquely identifying contacts in a Windows Phone Address Book

问题描述

考虑以下情况：

• 我省从随机跟X的地址簿导入ISO存储数据


• 我离开这个应用程序，并在地址簿中修改联系X


• 即将返回给应用程序，我怎么能确定在ISO寄存联系X是一样的联系我只是在地址簿中修改的X？

我的本​​意是用户的地址簿数据定期复制到异储存，然后同步它与服务器。我只是在做读操作，这是完全允许的，如果给予授权。

My intention is to periodically copy a user's address book data into Iso Storage and then sync it with a server. I'm only doing READ operations, which are fully permitted, if given authorization.

的问题是，联系人ID是私人领域，我无法使用联系人存储库（具有公共标识）。

The problem is that the Contact ID is a private field, and I cannot use Contact Stores (which have public IDs).

此外，WP通讯录没有内容规则，这意味着你可以有没有名字，请用10个电话号码，没有电话号码等，所以服用件的内容的唯一标识符，因为一致性不能保证将不工作。

Also, WP Contacts don't have content rules, meaning you can have contact with no name, with 10 phone numbers, with no phone numbers, etc, so taking a piece of content as a unique identifier will not work since consistency is not guaranteed.

哈希代码也不会因为在修改的有代码的一个修改的对象结果的工作。

Hash Codes will also not work since the a modified object results in a modified has code.

任何帮助深表感谢。

推荐答案

找到了答案 - 谢谢一个相关的问题在这里公布。

Found an answer - thanks to a related question posted here.

我反编译Microsoft.Phone DLL，似乎Contact.GetHashCode实际返回Contact.ID值。行为已被证实为预期的各种设备，并在模拟器上工作。

I decompiled the Microsoft.Phone DLL and it seems that Contact.GetHashCode actually returns the Contact.ID value. Behavior has been confirmed to work as expected on various devices and on the emulator.

所有这些人谁一贯坚持，开发商不应该被允许访问信息，如联系人ID - 请记住，用户联系访问权限的用户可以在市场上被拒绝。当我发展，我假设用户完全了解什么他惹祸，因为我走的时候，写一个有意义的描述和MS确实好验收测试。如果用户突然的现实应用打破他的隐私这不是我的问题，作为一个开发者。

All those people who consistently insist that developers should not be allowed access to information such as the contact ID - please bear in mind that users Contact Access permission can be denied in the marketplace. When I'm developing, I'm assuming the user fully understands what he's getting himself into, since I take the time and write a meaningful description and MS does good acceptance testing. If the user suddenly realities the app "breaks his privacy" IT'S NOT MY PROBLEM AS A DEVELOPER.

最后一段被我看到一对夫妇的答案的事实动机制定类似开发者不需要这些功能，他们违反隐私。

The last paragraph is motivated by the fact that I saw a couple of answers formulated something like "devs don't need these features, they break privacy".

这篇关于唯一地标识在Windows话机通讯录的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！