Serialize the dynamic object.

[seanmars]

It will get the non-yaml string when serialize the dynamic object.

dynamic o = new ExpandoObject();
o.name = "foo";
var serializer = new Serializer();
System.Console.WriteLine(serializer.Serialize(o));

will get

!System.Dynamic.ExpandoObject,%2520System.Linq.Expressions,%2520Version=4.2.1.0,%2520Culture=neutral,%2520PublicKeyToken=b03f5f7f11d50a3a
name: foo

Env(dotnet --info):

.NET Core SDK (reflecting any global.json):
 Version:   2.1.400
 Commit:    8642e60a0f

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.13
 OS Platform: Darwin
 RID:         osx.10.13-x64
 Base Path:   /usr/local/share/dotnet/sdk/2.1.400/

Host (useful for support):
  Version: 2.1.2
  Commit:  811c3ce6c0

.NET Core SDKs installed:
  2.1.400 [/usr/local/share/dotnet/sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

[xoofx]

yes. This is by design. The system has to be able to deserialize from it. Otherwise you need to specify the type of the expando object to the Serialize method (something like Serializer.Serialize(o, typeof(DynamicObject))), so that it won't dump anything.

[seanmars]

Thank you for your explanation.