Custom Classes and Lists of Objects

[zackrspv]

I am curious, being able to track submitted orders (IOrder objects), in a list in a structured format is rather simple (conceptually), however, doesn't seem to work nicely here in NT. For example, from my experience with C# and MVC, I can do something like this:

public class APosition
{
        public IOrder Entry { get; set; }
        public IOrder Target { get; set; }
        public IOrder Stop { get; set; }
        public int EntryId { get; set; }
        public Pro9Position() {}
}

APosition MyPositions = new List<APosition>();

Which, of course, compiles without issue. And, when I submit orders I can actually add to my list with the necessary IOrder object, and all is well.

However, when I try to enable this for strategies, etc, I of course, receive Serialization errors, due to the fact that IOrder is an interface.

If I change it to 'Order', which technically isn't supported, and cast the SubmitOrder() methods to (Order), it also compiles without issue, but the Serialization errors crop up stating that Order.Account.Connection isn't serializeable due to the fact that Order.Account.Connection doesn't implement IConnection.

Thus to me, it seems like we cannot have a LIST object of orders that we can quickly query and track.

Is this correct?

[bltdavid]

However, when I try to enable this for strategies, etc, I of course, receive Serialization errors, due to the fact that IOrder is an interface.

Make the APosition class private?

[bltdavid]

Is MyPositions public or private?
Is it declared inside your Strategy based class?

Ultimately, what you need to do is tell the serializer to ignore the public property/variable that it is attempting to serialize.

You'll do that by making it private (instead of public) or by adding [XmlIgnore()] attribute to the variable or property.

[koganam]

I am curious, being able to track submitted orders (IOrder objects), in a list in a structured format is rather simple (conceptually), however, doesn't seem to work nicely here in NT. For example, from my experience with C# and MVC, I can do something like this:

public class APosition
{
        public IOrder Entry { get; set; }
        public IOrder Target { get; set; }
        public IOrder Stop { get; set; }
        public int EntryId { get; set; }
        public Pro9Position() {}
}

APosition MyPositions = new List<APosition>();

Which, of course, compiles without issue. And, when I submit orders I can actually add to my list with the necessary IOrder object, and all is well.

However, when I try to enable this for strategies, etc, I of course, receive Serialization errors, due to the fact that IOrder is an interface.

If I change it to 'Order', which technically isn't supported, and cast the SubmitOrder() methods to (Order), it also compiles without issue, but the Serialization errors crop up stating that Order.Account.Connection isn't serializeable due to the fact that Order.Account.Connection doesn't implement IConnection.

Thus to me, it seems like we cannot have a LIST object of orders that we can quickly query and track.

Is this correct?

Are you trying to serialize APosition objects?