My generic method needs to serialize the object passed to it, however just insisting that it implements ISerializable doesn't seem to work. For example, I have a struct returned from a web service (marked with SerializableAttribute) that serializes to xml just fine, but, as expected, the C# compiler complains.
Is there a way I can check the object is serializable before attempting to serialize it, or, better still, a way of using the where
keyword to check the object is suitable?
Here's my full method:
public static void Push<T>(string url, T message) where T : ISerializable { string xml = SerializeMessage(message); // Send the message to Amazon SQS SendMessageRequest sendReq = new SendMessageRequest { QueueUrl = url, MessageBody = xml }; AmazonSQSClient client = new AmazonSQSClient(S3User, S3Pass); client.SendMessage(sendReq); }
And SerializeMessage:
private static string SerializeMessage<T>(T message) { XmlSerializer xmlSerializer = new XmlSerializer(typeof(T)); using (StringWriter stringWriter = new StringWriter()) { xmlSerializer.Serialize(stringWriter, message); return stringWriter.ToString(); } }
If this isn't possible, what's the best way to perform a check that an object is serializable at runtime?
You can specify one or more constraints on the generic type using the where clause after the generic type name. The following example demonstrates a generic class with a constraint to reference types when instantiating the generic class.
So here is the list of some of the constraints that you can add to the generic classes, using the where keyword: Restrict the generic class to use the type parameter of value or reference type only (as we discussed above). Restrict the type parameter T, to be implementing the specified interface.
Declaring those constraints means you can use the operations and method calls of the constraining type. If your generic class or method uses any operation on the generic members beyond simple assignment or calling any methods not supported by System. Object, you'll apply constraints to the type parameter.
Value type constraint If we declare the generic class using the following code then we will get a compile-time error if we try to substitute a reference type for the type parameter.
You can't do this totally via generic constraints, but you can do a couple things to help:
1) Put the new() constraint on the generic type (to enable the ability to deserialize and to ensure the XmlSerializer doesn't complain about a lack of default ctor):
where T : new()
2) On the first line of your method handling the serialization (or constructor or anywhere else you don't have to repeat it over and over), you can perform this check:
if( !typeof(T).IsSerializable && !(typeof(ISerializable).IsAssignableFrom(typeof(T)) ) ) throw new InvalidOperationException("A serializable Type is required");
Of course, there's still the possibility of runtime exceptions when trying to serialize a type, but this will cover the most obvious issues.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With