ListView IsRefreshing & IsPullToRefreshEnabled is not found in Xamarin.Forms - xamarin.forms

We are not able to find the below events in Xamarin.Forms ListView Control.
Error:
'xamarin.forms.ListView' does not contain definition for '**IsRefreshing**'
'xamarin.forms.ListView' does not contain definition for '**IsPullToRefreshEnabled**'
Note: We are using the Xamarin Latest Version (Xamarin 4.0.0.1717).
Kindly Suggest on this.

This error is due to Xamarin.Forms Dll is not updated to latest version from Visual Studio (I have updated only from Visual studio and shows up-to date).
By Opening the same source in Xamarin Studio and updating the Xamarin Forms Dll, the above properties are retrieved.

You'll see that you're using Xamarin.Forms 1.3 when you click the properties of Xamarin.Forms.Core.dll from project references.
For upgrading it(in VS) right click the solution and click Manage Nuget Packages. Then update Xamarin.Forms dll's.

Related

Xamarin Forms page are missing in Visual Studio 2019 to add

I have installed Xamarin in visual studio but i am not getting xamarin.Form. My old project is running but when i try to add new page i am not finding xamarin.forms page there to add. I have uninstalled and installed two times but this option is not coming .
Can you help me to find out this issue.
Below component is installed
Really surprise they forget to add this. Micorsoft has fixed this issue let's wait for next release. Microsoft developer community

Is this ExportRenderer still required in Xamarin Forms 4.4 +

I have a couple of questions about the WKWebview in Xamarin Forms
1) From https://github.com/xamarin/Xamarin.Forms/pull/3346:
To opt-in to using WkWebView add the following to the AssemlyInfo.cs file of your iOS C# project file
[assembly: ExportRenderer(typeof(WebView), typeof(Xamarin.Forms.Platform.iOS.WkWebViewRenderer))]
Is this assembly still necessary to use in Xamarin Forms 4.4? Apparently WKWebView is the default view in XF4.4 so it's unnecessary?
2) Are there any visual changes between the UIWebView and the WKWebview? I updated my app from XF3.4 to 4.4 because I heard of the WebView change, but there doesn't seem to be any visual difference, but there is one weird bug in 4.4 where the loading icon won't disappear from the middle of my screen even though my page appears to have loaded properly...
Thanks!
From the latest document of webView, WKWebView has replaced UIWebView since Xamarin.forms 4.5:
Starting in April 2020, Apple will reject apps that still use the
deprecated UIWebView API. While Xamarin.Forms has switched to
WKWebView as the default, there is still a reference to the older SDK
in the Xamarin.Forms binaries. Current iOS linker behavior does not
remove this, and as a result the deprecated UIWebView API will still
appear to be referenced from your app when you submit to the App
Store.
A preview version of the linker is available to fix this issue. To
enable the preview, you will need to supply an additional argument
--optimize=experimental-xforms-product-type to the linker.
The prerequisites for this to work are:
Xamarin.Forms 4.5 or higher – Pre-release versions of Xamarin.Forms
4.5 can be used.
Xamarin.iOS 13.10.0.17 or higher – Check your Xamarin.iOS version in
Visual Studio. This version of Xamarin.iOS is included with Visual
Studio for Mac 8.4.1 and Visual Studio 16.4.3.
Remove references to UIWebView – Your code should not have any
references to UIWebView or any classes that make use of UIWebView.
Have a look at this thread would help.
For your first question, I think it is no longer needed in Xamarin.forms 4.5+.
For your second question, if you have any question, you can open an issue in Github of Xamarin.forms.

How do i add UWP to xamarin forms in VS2019?

I try to create a new project(xamarin form) in vs2019, and discovered that the UWP template is missing.
I created the project in vs2017 yet it did not work. now I have added a UWP project to the xamarin form app created using vs2019, how do I link them, how do I connect(refrence) the UWP to the portable library?
I want to make use of the portable library in xamarin forms that ha UWP in it, like vs2017 versions
In VS 2019 version 16.0.0 UWP head project have been removed from the Xamarin.Forms app template. However, if you install latest version of VS 2019 (16.0.1) that option should be available to you. According to the release notes:
Add option for Windows (UWP) platform when creating new Xamarin.Forms project from 'Mobile App (Xamarin.Forms)' project template.
Other then that you could just simply add UWP as a separate project and set it up for Xamarin.Forms.

Updating Component References to NuGet

With recent stable Visial Studio 2017 Enterprise Update v15.6.2 I get that nag message when the Xamarin.Forms solution is loaded.
I followed the How to update link but still get that message. The Components folder is in the solution directory and the dll is included as Reference.
That is my Visual Studio Version
Thanks for any help to get rid of the Time to update message dialog.

Visual Studio App Center - Duplicate 'EmbeddedResource' items were included when building Xamarin Forms app?

When building a Xamarin Forms app in Visual Studio App Center it complains about the embedded xaml-files when using netstandard2.0.
Locally with updated Visual Studio and Xamarin Forms it works perfect to build and run.
(CheckForDuplicateItems target) ->
/usr/local/share/dotnet/sdk/2.0.3/Sdks/Microsoft.NET.Sdk/build/Microsoft.NET.Sdk.DefaultItems.targets(276,5):
error : Duplicate 'EmbeddedResource' items were included. The .NET SDK
includes 'EmbeddedResource' items from your project directory by
default. You can either remove these items from your project file, or
set the 'EnableDefaultEmbeddedResourceItems' property to 'false' if
you want to explicitly include them in your project file. For more
information, see https://aka.ms/sdkimplicititems.
How should xaml-files be added to the project if not as embedded?
UPDATE:
The same error is present using VSTS and Hosted Mac Agent
Edit your .csproj file and remove the ItemGroup that contains the EmbeddedResource.
This resolved the issue from me but the original answer came from Xamarin Forums

Resources