LottieSharp.WPF.LottieAnimationView threw an exception in Version 2.0.1
See original GitHub issueHello. After installing the LottieSharp(V 2.0.1), and adding the namespace in the xaml file and the corresponding tag, it gives the following message ===================== MY Code ===================== NameSpace: xmlns:lottie=“clr-namespace:LottieSharp.WPF;assembly=LottieSharp”
<lottie:LottieAnimationView
Width="200"
Height="300"
HorizontalAlignment="Center"
VerticalAlignment="Center"
AutoPlay="True"
FileName="C:\Res\Images\Public\data_not_found.json"
RepeatCount="-1" />
Exeption Error:
System.Windows.Markup.XamlParseException: ‘The type initializer for ‘LottieSharp.WPF.LottieAnimationView’ threw an exception.’
------ ↓ and ↓ -------
FileNotFoundException: Could not load file or assembly 'WindowsBase, Version=6.0.2.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35'. The system cannot find the file specified.
*** One thing I have to say is that the json file is available in the specified path.
Has anyone had this problem?
===================== MY Code =====================
Issue Analytics
- State:
- Created a year ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
quicoli/LottieSharp: Lottie animations for WPF applications
Version 2.0.1. Fixed issue #57. Fixed issue with animation details not being displayed in databinding. Properties, Methods and Events ...
Read more >Unable to catch exception due to parsing errors in json #999
I need to ensure in that case the app doesn't crashes or library throws appropriate exception that can be caught.
Read more >Lottie animation slows down my other native wpf animations
I am using them in button, so my solution for now is, when the button appears, to load it: animation = new LottieAnimationView();...
Read more >Using Lottie images in WPF .Net5 - Microsoft Q&A
My project is WPF and target framework is .NET 5.0. I want to use Lottie images. I wanted to use Lottie without converting...
Read more >Exception when a WPF window is displayed
When WPF detects this, it is considered a fatal condition and WPF purposely calls System.Environment.FailFast , which throws a System.
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 Free
Top 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
I had the same problem
See release 2.2.0