Repository navigation
[AoT] Compile error if only one StaticContext exist and in global namespace #1031
Description
Describe the bug
In the project, if there is a unique class with YamlStaticContext attribute, and this class is in the global namespace, while there are other classes with YamlSerializable attribute, the compilation will fail.
To Reproduce
- Create a C# console project and enable NativeAoT publish. ( Dont trigger
Do not use top-level statements) - Add necessary package from nuget. (
YamlDotNetandVecc.YamlDotNet.Analyzers.StaticGenerator) - Delete all template content in
Program.cs - Paste code.
Console.WriteLine("Hello world");
[YamlDotNet.Serialization.YamlSerializable]
public class Model {}
[YamlDotNet.Serialization.YamlStaticContext]
public partial class YamlContext : YamlDotNet.Serialization.StaticContext {}Build output here
$ dotnet build
Restore complete (2.2s)
BugReproduceProject failed with 1 error(s) (0.4s)
C:\BugReproduceProject\obj\Debug\net9.0\YamlDotNet.Analyzers.StaticGenerator\YamlDotNet.Analyzers.StaticGenerator.TypeFactoryGenerator\YamlDotNetAutoGraph.g.cs(8,10): error CS1001: Identifier expected
Build failed with 1 error(s) in 2.9s
Activity
fix aaubry#1031
fix aaubry#1031
EdwardCooke commentedon Jan 18, 2025
I’ll be sure to merge in that or with the next release. I’m thinking it’ll be this weekend if I have time.
dogdie233 commentedon Jan 19, 2025
Thank you, i put my context in a namespace as a temporary fix
docs: aaubry/YamlDotNet#1031
Merge pull request #1033 from dogdie233/fix-1031
aaubry commentedon Apr 10, 2026
A fix for this issue has been released in version 17.0.0.
aaubry commentedon Apr 10, 2026
A fix for this issue has been released in version 17.0.0.