Comments on: C# – “Type is not resolved for member” SerializationException in Connection.get_LocalIP() RESOLVED! http://finite.mikeandcorinne.com/2010/03/c-type-is-not-resolved-for-member-serializationexception-in-connection-get_localip-resolved/ Mike's thoughts on programming and tech Tue, 16 Mar 2010 23:25:13 +0000 hourly 1 http://wordpress.org/?v=3.0 By: jmorris http://finite.mikeandcorinne.com/2010/03/c-type-is-not-resolved-for-member-serializationexception-in-connection-get_localip-resolved/comment-page-1/#comment-15 jmorris Tue, 16 Mar 2010 23:25:13 +0000 http://finite.mikeandcorinne.com/2010/03/c-type-is-not-resolved-for-member-serializationexception-in-connection-get_localip-resolved/#comment-15 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 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

]]>