SEHException when serializing value types problem fixed on Whidbey

Just got an answare for the problem reported in this entry.

The product team looked at the issue and the problem is as follows

Issue has to do with having a declarative security demand on a method that
is the implementation of an interface AND the type that implements the
interface is a value type

The problem has been fixed in whidbey. For now the workaround suggested is
to Convert the declarative demand to an imperative demand inside
Please let me know  if you need any more information.


Anand Balasubramanian
Microsoft, Visual Basic .NET

You can check out the entire discussion thread here.

You may also like...