CachedImageRenderer is not available for registration in .NET Standard
See original GitHub issueSteps to Reproduce
- Install VS2017 15.5.3
- Create a blank Xamarin.Forms 2.5.0.122203 app with .NET Standard option
- Install FFImageLoading 2.3.4 Nuget package
- Add
CachedImageRenderer.Init();
toMainActivity
andAppDelegate
- Observe that
Forms
is not recognizable by VS when you import- FFImageLoading.Forms.Touch
- FFImageLoading.Forms.Droid
Expected Behavior
Need to be able to register CachedImageRenderer
so FFImageLoading
can be used.
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
c# - Please call CachedImageRenderer.Init method in a ...
Call CachedImageRenderer.Init after global::Xamarin.Forms.Forms.Init(); in FinishedLaunching method present in AppDelegate.cs file of iOS ...
Read more >Xamarin.FFImageLoading.Forms 2.2.8
Xamarin Forms plugin to load images quickly and easily on Xamarin.Forms. Features: - Xamarin.Forms - iOS / Android / Windows (WinRT, ...
Read more >Xamarin Community Forums - RSSing.com
Using FFImageLoading CachedImage however is not showing the image when I run my app whereas Image (Xamarin Image View) is showing it fine....
Read more >NET Framework technologies unavailable on .NET 6+
Several technologies available to .NET Framework libraries aren't available for use with .NET 6+, such as app domains, remoting, and code ...
Read more >export huge PDF
I have a urgent need for exporting a 1g pdf but got out of memory error in the following code. JRExportManager.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I downgraded FFImageLoading to 2.3.2 and it works fine. So there is no problem with .NET Standard 2.0 and there is something wrong with 2.3.4 version of FFImageLoading.
I’ll close this one as I cannot reproduce it on a new project. Please attach a repo if it’s still happening.