Deprecate PullToRefreshListView control

[nmetulev]

Once the platform’s native pull-to-refresh control is released, the PullToRefreshListView control will need to be deprecated and leverage the new platform control whenever possible.

We should attempt to add a new property called UseRefreshContainerWhenPossible to enable use of the platform control on devices where it is available.

[nmetulev]

@kbrons is working on this

[nmetulev]

PR merged

[Trolldemorted]

@nmetulev If you use a PullToRefreshListView in an UWP project (min build 15063 (Creators Update), target build 17134 (W10 April Update)), you see warnings because of this deprecation:

'PullToRefreshListView' is obsolete: 'The PullToRefreshListView will be removed in a future major release. Please use the RefreshContainer control available in the 1803 version of Windows

Since you refuse to ship any updates beyond 15063 to W10M, UWP developers who don't want to exclude smartphones are stuck with that minimum version. What are we supposed to do with the PullToRefreshListView in the future? Are you serious about removing it?

[nmetulev]

We are. You can still continue using the PullToRefreshListView by using the source directly (you can find it in our releases), but we will remove it from the nuget packages in the future and we will not fix bugs

[hupo376787]

Why MS does not consider about our developers' feelings. Change is a good thing, but always change must be bad.

[nmetulev]

@hupo376787, it doesn't make sense to support multiple versions of the same functionality. In this case, with the upcoming release of the Windows UI library (which also works on older versions of Windows 10), you can use the RefreshContainer in place of the PullToRefreshListView and we even have a guide on how to do it.

[Trolldemorted]

@nmetulev does "older versions" include w10 mobile?

[nmetulev]

Not sure what their minimum version is, but if it works on Creators Update, then yes.

[hupo376787]

RefreshContainer's min version is 1803, so the mobile device users will never never get it.

[JustinXinLiu]

RefreshContainer will be part of the new Windows UI package which will work on earlier versions of Windows 10.

[hupo376787]

Following this guide, getting-started.

And according to my test, RefreshContainer can't work on win 10 mobile 15063. I don't have other versions, so the result is not known.

Windows.UI.Xaml.Markup.XamlParseException: 'XAML parsing failed.'

My test project gayhub

[JustinXinLiu]

First, you are not using the control from the nuget at all because you are not setting the target version correctly:

Important: To use the Windows UI Library, your project’s Min version must be 14393 or higher and the Target version must be 17134 or higher.

However, even if you do so, the project will throw the following error:

System.TypeLoadException: 'Could not find Windows Runtime type 'Microsoft.UI.Private.Controls.IRefreshInfoProvider'.'

@nmetulev, could you please let the team know?

[hupo376787]

Yes, I tried. See my first comment before edited. Same error.

[JustinXinLiu]

@hupo376787, no, you cannot just target 16299... If you target 16299, it is still going to use the control in the SDK, NOT the one from the nuget package. You need to make sure the target version is at least 17134.

It will still not work and this is another issue though. We are already looking into this.