[W8.1] [Xaml]联系人选择器扩展声明在Win10上未按预期工作 [英] [W8.1][Xaml] Contact Picker Extension Declaration not working as expected on Win10

问题描述

正如标题所示，我发现在完全更新的Windows 10 VM中，从Win 10商店运行我的Windows 8.1 Universal应用程序[xaml]时存在兼容性问题。

As the title suggests, I'm seeing a compatibility issue running my Windows 8.1 Universal app [xaml] from the Win 10 store in a fully updated Windows 10 VM.

当我从我的应用程序启动联系人选择器（并在appxmanifest中声明了联系人选择器扩展）时，"人员应用程序"在Win10中启动，我的联系人列在Outlook和Office365帐户中。

When I launch the contact picker from my app (and have the Contact Picker Extension declared in the appxmanifest) the "People App" in Win10 is launched with my contacts listed from Outlook and Office365 accounts.

这与在Windows 8.1中从商店下载的相同确切应用包的行为相反人员选择器在我的应用程序中就地打开一个公共联系人选择器，然后我可以从我的应用程序自己的联系人
列表中选择联系人。 （我的应用程序提供联系人，联系人选择器提供其他应用程序可以访问的通用UI ...）

This is sort-of contrary to the behaviour of the same exact app package downloaded from the store in Windows 8.1, where launching the people picker opens a common contact picker in-place in my app where I can then choose the contacts from my app's own contact listings. (my app provides the contacts, the Contact Picker provides a common UI that other apps can access...)

主要关注的是，在几天内，已购买的客户我的应用程序迁移到Windows 10（无论如何都处于当前状态）将无法看到他们的应用程序联系人，应用程序将变得无用。

The main concern is that in a couple of days, the clients that have purchased my app that migrate to Windows 10 (in it's current state, anyway) won't see their app contacts and the app will become useless.

对我来说，似乎Windows 10不是关于应用程序清单中的联系人选择器扩展声明，或者人员应用程序可能不完整，或者我的应用程序包中有些东西我对Win10做错了。 注意
它在Windows 8.1中100％工作并且已经存在了将近一年。

To me, it appears either that Windows 10 isn't yet regarding the Contact Picker extension declaration in the app's manifest, or perhaps the people app isn't complete, or there's something in my app package that I'm doing wrong for Win10.  Note that it is working 100% in Windows 8.1 and has for nearly a year.

我看不到
Windows.ApplicationModel.Contacts.Provider 命名空间，表示需要更改代码  Windows 8.1 Universal应用程序中的联系选择器扩展声明是否存在任何已知问题，特别是在Windows 10预发行版中，我应该知道
？ 我不得不认为很多依赖于此的应用会突然变得不相容。

I can't see anything around the Windows.ApplicationModel.Contacts.Provider namespace that indicates a change of code is required.  Is there any known issue with the Contact picker extension declaration in Windows 8.1 Universal apps specifically on Windows 10 pre-releases that I should be made aware of?  I have to think a lot of apps relying on this will suddenly be incompatible.

有什么建议吗？

Windows.ApplicationModel.Contacts.ContactPicker contactPicker = new Windows.ApplicationModel.Contacts.ContactPicker();
                contactPicker.DesiredFieldsWithContactFieldType.Add(Windows.ApplicationModel.Contacts.ContactFieldType.Address);
                contactPicker.DesiredFieldsWithContactFieldType.Add(Windows.ApplicationModel.Contacts.ContactFieldType.PhoneNumber);
                contactPicker.DesiredFieldsWithContactFieldType.Add(Windows.ApplicationModel.Contacts.ContactFieldType.Email);

                Windows.ApplicationModel.Contacts.Contact contact = await contactPicker.PickContactAsync();

[/编辑]

Darin R。

推荐答案

Hello Darin，

Hello Darin,

根据您的描述，我使用官方示例进行了测试：联系Picker app示例，是的，在Windows 10中，它仅提供默认UI以供使用选择联系信息。对于这种情况，我认为它是由于虽然api看起来仍然是
仍然相同，但是，系统从Windows 8 / 8.1更改为Windows 10，所以我认为细节 
的实施也发生了变化。对于您遇到的情况，我建议您可以向团队发布反馈，以通过内置的反馈工具进行确认：

With your description, I made a test with the official sample: Contact Picker app sample and yes, in windows 10, it only provides a default UI to let use select the contact information. For this scenario, I think it is caused by that although the api seems to be still same, however, the system are changed from windows 8/8.1 to windows 10, so I think the detail  implementation are changed as well. For the scenario you encountered, I suggest you could post a feedback to the team to confirm this by the built-in feedback tool:

http://windows.microsoft.com/en-us/windows/preview-updates-feedback-pc

问候。

这篇关于[W8.1] [Xaml]联系人选择器扩展声明在Win10上未按预期工作的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！