Comments on: C# – “Type is not resolved for member” SerializationException in Connection.get_LocalIP() RESOLVED!

By: Julian

Julian — Thu, 07 Jul 2011 04:15:04 +0000

I solved this problem setting the specific property in CallContext to null. In my case I use Remoting to consume Business Objects and this problem happen because the my custom Principal object is put in CallContext. I set null in CallContext thgouh the SetData method ands works.
The problem happen when calling of Response.Flush();

By: metal model cars

metal model cars — Sat, 28 May 2011 01:25:13 +0000

undefined

By: John1596

John1596 — Mon, 28 Feb 2011 04:02:34 +0000

Very nice site!

By: John1596

John1596 — Mon, 28 Feb 2011 04:02:18 +0000

Very nice site! [url=http://oixapey.com/aqvoxr/2.html]is it yours too[/url]

By: John1596

John1596 — Mon, 28 Feb 2011 04:02:02 +0000

Very nice site! is it yours too

By: jmorris

jmorris — Tue, 16 Mar 2010 23:25:13 +0000

Funny, I just ran into this. It actually happens when you assign the IPrincipal implementation to the Thread.CurrentPrincipal property. Setting the Context.User field is fine, however. It also only failed in my case when I called the Page.ClientScript.GetCallbackEventReference method!

I tried your suggestion with the ComVisible and deriving from MarshalByRefObject and then ran into trouble with serialization/deserialization using the DataContractJsonSerializer. I stopped short there and just removed the Thread.CurrentPrincipal = principal code, since this is a cassini specific error and I’ll be on IIS next week.

-Jeff