tag:blogger.com,1999:blog-29842129.post2833122703533615379..comments2023-07-24T09:35:29.276-06:00Comments on Programming Joy: .NET Remoting Causes Security Exception After Upgrade to .NET 4.0Dickyhttp://www.blogger.com/profile/00321030386495287983noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-29842129.post-69368486864826753442013-12-23T17:06:10.811-07:002013-12-23T17:06:10.811-07:00Thank you - I have also been looking for this solu...Thank you - I have also been looking for this solution - bringing an old remoting app from 1.3 to 4.5Unknownhttps://www.blogger.com/profile/16181060750268229990noreply@blogger.comtag:blogger.com,1999:blog-29842129.post-86567124984810642772011-12-04T05:44:07.742-07:002011-12-04T05:44:07.742-07:00Thank you, thank you, thank you! I realize .NET Re...Thank you, thank you, thank you! I realize .NET Remoting is no longer considered relevant, but I just found myself in the same situation and spent 2 days banging my head against the wall until I found your post.<br /><br />For me the issue cropped up when a reflection call was made inside the ISerializable constructor, even though reflection worked perfectly fine everywhere else. Adding typeFilterLevel = "full" fixed the issue.Joenoreply@blogger.com