yaml.Documents[].RootNode is YamlScalarNode instead of YamlMappingNode in VS2022 console project about yamldotnet

[EdwardCooke]

In your top screen shot your casting to a YamlMappingNode before checking the type. In your second screenshot regardless of the type your still casting to YamlMappingNode. My suspicion is both throw an exception.

[EdwardCooke]

YamlMappingNode would come after the yamlscalar

[RadovanPodhradskySk]

1st picture was from VS2022 new console application
2nd picture was from VS2022 with opened console application created in VS2019

it was only example method in both solutions

I'm sending you short yaml file example (included in VS2022 solution archive), which has different AllNodes in console application created in VS 2022 and in VS 2019 console application opened in VS2022

I'm sending you archive with simple VS2022 WinForms application example and snippet of yamlNode.AllNodes View (Visualizer View) on Line30 in Form1.cs
AllNodes usually shows whole yaml structure in Visual Studio Visualizer

There is no possibility to traverse from RootNode typed as YamlScalarNode to another node in structure of UnitDescTestShort.yaml file.

YamlLoadExampleVs2022.zip

VS 2022 Professional version installed on my virtual Win10 is 17.6.4

Maybe my description is little bit more clear now.

[EdwardCooke]

Thanks, the version of Visual Studio shouldn't effect anything, it would be the version of .net that was being targeted by your project. I'll take a look at this tonight and let you know what I see.

[EdwardCooke]

In your zip file, In the ReadFile method you're creating a StringReader instead of a StreamReader.

[RadovanPodhradskySk]

Really, It was StringReader instead of StreamReader, I don't know how it was written, maybe with IntelliSense. I thought, that I copied these several lines from source file, where StreamWriter is used and behaviour is proper. Thanks for your attention to this my "issue". After using of StreamReader, AllNodes contains all yaml file nodes and RootNode type is YamlMappingNode. You are doing good job to create and support YamlDotNot over YAML standard. I use it in several company projects with very good experience.