Unable to generate schema for type defined in .NET 5 assembly
See original GitHub issueHi,
I’m probably doing something stupid but I’m unable to generate avro schema using dotnet avro cli tool.
Command I’m executing:
dotnet avro create -a bin/Debug/net5.0/Events.dll -t Events.AccountEvent
And error I’m getting in response:
The type could not be found. You may need to provide additional assemblies.
So question is what am I doing wrong here? 😞 Thanks in advance!
Here is decompiled assembly in ILSpy:
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
The type is defined in an assembly that is not referenced ...
When you get this error, it means that code you are using makes a reference to a type that is in an assembly,...
Read more >XSD.exe does not work with .NET Core assemblies #61319
XSD.exe seems to be a .NET Framework executable. If you try to give it a .NET Core assembly to generate XSD files from,...
Read more >Assembly Manifest doesn't match reference
This article helps you resolve an error (The located assembly's manifest definition does not match the assembly reference) that occurs when a ...
Read more >Swashbuckle.AspNetCore
In versions prior to 5.0.0 , Swashbuckle will generate Schema's (descriptions of the data types exposed by an API) based on the behavior...
Read more >How to resolve “Could not load file or assembly … or one of its ...
When you build solution there can be one Newtonsoft.JSON.dll in bin/debug or bin/release folder. fuslogvw.exe is assembly binding log viewer (installed with ...
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
Yeah, the next major release will bump it to .NET 5. I’ll also keep this open as a bug since we’d want this to fail with a better message.
Thanks for your patience on this; the 7.1.0 release later today will add
net5.0
as a CLI target framework.