Confusing Developer Experience When Unknown Assemblies Are Encountered
See original GitHub issueFrom this comment: https://github.com/ExtendedXmlSerializer/home/issues/543#issuecomment-948049560
Serializer still breaks when defaulting to fusion.dll. In such cases we should default to Assembly.LoadWithPartialName
.
Issue Analytics
- State:
- Created 2 years ago
- Comments:19 (11 by maintainers)
Top Results From Across the Web
The located assembly's manifest definition does not match ...
This Microsoft article states that assemblies found in the GAC are not copied locally during a build, so you might need to remove...
Read more >Error message: EVP_MD_size assembly:<unknown ...
Duplicati uses it now, and that (to this non-C#-developer) is my suspect on issue cause, but it means to fall back better. obtain...
Read more >An update on the LSP-powered, Visual Studio Code C# ...
I'm using extension without C# Dev Kit . Seems like it works, but it completely did not see types from framework assemblies, e.g....
Read more >Bring back the 'Developer News' on startup
I feel like the new start page could still come up as a tab with the new fancy UI and still include the...
Read more >The 10 Most Common Mistakes in C# Programming
Don't fall into one of these C# programming mistakes that even savvy developers can find problematic. Read on to see all 10.
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
Lovely, Mike! Thanks for your legendary fast and effective support!
Woohoo… those are the kind of problems I like. 😁
Indeed, as you found out. FWIW I have updated the message that is thrown to make it more obvious which assembly is causing the problem. You can find that here until we deploy to NuGet next Tuesday: https://github.com/ExtendedXmlSerializer/home/pull/559#issuecomment-948471674