Reply to thread

Message: <blockquote data-quote="TheGeneral" data-source="post: 471660" data-attributes="member: 73182">Going generic in your interface doesnt mean you are required to have a parameterless constructor. Just do something like this:[ICODE]typeof(MessageType).GetConstructor(new[] { typeof(IClientMessage)}).Invoke(new[]{message})[/ICODE]And wherever you register your messages you can check if that type has a constructor that accepts [ICODE]IClientMessage[/ICODE]The point of a constructor is so that the object is fully constructed and initialized, ready to be used. Having an extra function to be an hardrequirement to be called on that specific object to initialize it, is bad practice and defies the purpose of having a constructor. A better approach would be to have a static parse function that fills out the parameters values through the constructor.</blockquote>