使用protobuf-net序列化对象数组以供C++使用

我已经按照下面的答案中的指示构建了一些类，以便能够序列化泛型对象的列表；例如KeyValuePair和KeyValuePaire的实例。

不幸的是，GetProto（）方法生成的.proto文件似乎没有生成一个可以为C++正确解析的文件。为数组生成的子类型消息以"[]"作为后缀。为C++编译时，protocol.exe阻塞了"[]"。

由于protobuf的消息名称似乎是任意的（也就是说，它们实际上不包括在数据流中），有可能告诉protobuf-net在命名子类型时使用"_Array"而不是"[]"吗？或者，我是否应该采取其他途径，以便C++应用程序可以使用生成的.proto文件？

谢谢，

以下是相关代码和生成的proto文件。

基本类是：

[DataContract]
[ProtoInclude(101, typeof(KeyValuePairResponse<string>))]
[ProtoInclude(102, typeof(KeyValuePairResponse<int>))]
[ProtoInclude(103, typeof(KeyValuePairResponse<double>))]
[ProtoInclude(111, typeof(KeyValuePairResponse<string[]>))]
[ProtoInclude(112, typeof(KeyValuePairResponse<int[]>))]
[ProtoInclude(113, typeof(KeyValuePairResponse<double[]>))]
public abstract class KeyValuePairResponse
{
    protected KeyValuePairResponse() { }
    [DataMember(Order = 1, IsRequired = true)]
    public string Key { get; set; }
    public object Value
    {
        get
        {
            return this.ValueImplementation;
        }
        set
        {
            this.ValueImplementation = value;
        }
    }
    protected abstract object ValueImplementation { get; set; }
    public static KeyValuePairResponse<T> Create<T>(string key, T value)
    {
        return new KeyValuePairResponse<T>(key, value);
    }
}

通用类为：

[DataContract]
public sealed class KeyValuePairResponse<T> : KeyValuePairResponse
{
    public KeyValuePairResponse()
    {
    }
    public KeyValuePairResponse(string key, T value)
    {
        this.Key = key;
        this.Value = value;
    }
    [DataMember(Order = 2, IsRequired = true)]
    public new T Value { get; set; }
    protected override object ValueImplementation
    {
        get
        {
            return this.Value;
        }
        set
        {
            this.Value = (T)value;
        }
    }
}

GetProto<KeyValuePairResponse>()创建的.proto文件看起来像：

message KeyValuePairResponse {
   required string Key = 1;
   // the following represent sub-types; at most 1 should have a value
   optional KeyValuePairResponse_String KeyValuePairResponse_String = 101;
   optional KeyValuePairResponse_Int32 KeyValuePairResponse_Int32 = 102;
   optional KeyValuePairResponse_Double KeyValuePairResponse_Double = 103;
   optional KeyValuePairResponse_String[] KeyValuePairResponse_String[] = 111;
   optional KeyValuePairResponse_Int32[] KeyValuePairResponse_Int32[] = 112;
   optional KeyValuePairResponse_Double[] KeyValuePairResponse_Double[] = 113;
}
message KeyValuePairResponse_Double {
   required double Value = 2 [default = 0];
}
message KeyValuePairResponse_Double[] {
   repeated double Value = 2;
}
message KeyValuePairResponse_Int32 {
   required int32 Value = 2 [default = 0];
}
message KeyValuePairResponse_Int32[] {
   repeated int32 Value = 2;
}
message KeyValuePairResponse_String {
   required string Value = 2;
}
message KeyValuePairResponse_String[] {
   repeated string Value = 2;
}