You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
This happens both on a completely clean project and on a version that worked with version 4.5
on startup it gives an error
$exception {“Failed to load file or assembly \”GLWpfControl, Version=3.3.0.0, Culture=neutral, PublicKeyToken=null\” or one of their dependencies. An assembly with a strict name is required. (HRESULT exception: 0x80131044)": ‘GLWpfControl, Version=3.3.3.0.0, Culture=neutral, PublicKeyToken=null’} System.IO.FileLoadException
To Reproduce
Steps to reproduce the behavior:
Create new WPF App .Net Framework 4.8 or open an existing one
Add CartesianChart in .xaml (LiveChartsCore.SkiaSharpView.WPF 2.0.0-rc5)
Run App
See error
GLWpfControl is in the build folder, I don't understand why the problem occurs
Screenshots
Desktop (please complete the following information):
OS: Windows 11
Browser [e.g. chrome, safari]
Version 23H2
Additional context
WPF App, .Net Framework 4.8
The text was updated successfully, but these errors were encountered:
MINT-KISS
changed the title
Failed to load GLWpfControl on version 5.0
FileLoadException (LiveChartsCore version 5.0)
Jan 14, 2025
Related to mono/SkiaSharp#3111, I think I'll release a new version that does not references this bugged version of SkiaSharp, the issue only happens on Net framework.
Describe the bug
This happens both on a completely clean project and on a version that worked with version 4.5
on startup it gives an error
To Reproduce
Steps to reproduce the behavior:
GLWpfControl is in the build folder, I don't understand why the problem occurs
Screenshots
![image](https://private-user-images.githubusercontent.com/43280109/402937232-c0c60810-1aa5-4d0f-8d56-ce9a93768c92.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwNTQyNjEsIm5iZiI6MTczOTA1Mzk2MSwicGF0aCI6Ii80MzI4MDEwOS80MDI5MzcyMzItYzBjNjA4MTAtMWFhNS00ZDBmLThkNTYtY2U5YTkzNzY4YzkyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA4VDIyMzI0MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc1MDYyZjRiZWU5YjZmYThiNDNiODQ5YTJjZTczZTEzMWEwMDRmNGU2MTc1Y2M0N2UzYTI5NDAxMzNlMTIxNGYmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.G7npZwHx8fZPq6uLXbjXpP6p2FhLPK-C4N9RN9xYKYA)
Desktop (please complete the following information):
Additional context
WPF App, .Net Framework 4.8
The text was updated successfully, but these errors were encountered: