Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
UWP does not work when Targeting Windows build 10240
See original GitHub issueI have upgraded to the Latest version of Rg.popup V1.1.3.73-pre and my UWP has a target version and min version of Windows 10 build 10240
I then run my program on UWP and I start to get this error:
“System.IO.FileLoadException: Could not load file or assembly ‘System.Runtime.WindowsRuntime, Version=4.0.14.0, Culture=neutral, PublicKeyToken=b77a5c561934e089’. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)\r\n”
After digging around the internet the only mention of this version of the library I can find is here: https://github.com/dotnet/docs/issues/3644#issuecomment-343339458
Which states:
The update was only was published as part of Microsoft.NETCore.UniversalWindowsPlatform and you have to target Fall Creator’s Update or higher for the APIs I have listed above. That gets you the following version of the assembly (4.0.3.0 is the latest standalone):
System.Runtime.WindowsRuntime, Version=4.0.14.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
So essentially I think by using API’s from this latest version of the library it means that the minimum you can support is Fall Creators update
2 solutions:
- take the code that is using the latest API out of the plugin
- Microsoft release V4.0.14 as a seperate nuget (this would be the best solution as I would imagine there are probably other people / plugins that will be hitting this error pretty soon)
Issue Analytics
- State:
- Created 6 years ago
- Comments:11 (9 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@EmilAlipiev I am using .Net Standard 1.4. The only reason is because I am sharing this library with an old .Net Framework 4.5 project.
If you push your project to .Net Standard 2.0 you are forced to use Creators Fall Update
If you use .Net Standard 1.6. you can support Windows 10 10240 as a minimum.
The only reason I want to support the min version of Windows 10 is so I can say to my clients “it will work on any windows 10 machine” and don’t have to follow it up with (only if its fully up to date)
Hope that clarifies
Just wanted to say thanks for fixing this @rotorgames! Much appreciated!