Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a silverlight application with a service reference back to a Silverlight-Enabled WCF service. When I try to “new up” the WCF objects I get an exception about not having a constructor when I do the following.
Activator.CreateInstance(type, true);
However; this works:
Activator.CreateInstance(type);
Any idea why?
If your code does not have the appropriate
ReflectionPermissionbit (presumablyReflectionPermissionFlags.RestrictedMemberAccess) then the underlying reflection search for non-public members will bomb out.RestrictedMemberAccessis a very powerful permission and likely isn’t granted to any code running in a browser, with the possible exception of an assembly reflecting over itself and/or anything granted byInternalsVisibleToAttribute. Accessing private members of the Silverlight runtime libraries, for example, is prohibited by default policy.