Hey,
I tried the repro case on that bug and verified it works under .NET.
Then I removed the parameterless constructor. .NET borked.
That means, instead of using XmlReader.ReadContentAsObject(),
you would simply write like below.
IXmlSerializable x = (IXmlSerializable) Activator.CreateI
Varadhan,
Depending on exception on regular paths might lead to disastrous
performance.
Is this just a corner case for compatibility or this kind of situation might
happen often?
We might need to document this shortcoming of our stack.
Thanks,
Rodrigo
On Wed, Jul 30, 2008 at 10:56 AM, Veerapura
