如何让 Reflection.Emit 程序集访问生成程序集中的内部成员？
对于我的一个项目，我需要在运行时生成一些类，我认为使用 Reflection.Emit 来完成会相当简单，但是当我运行一些调用方法的生成代码时，我收到了 MemberAccessExceptions标记在发电机组件内部。 有什么方法可以告诉运行时动态程序集应该能够直接访问我自己的代码吗？ 我真的不想向我的图书馆的消费者公开暴露这些成员。
Regarding InternalsVisibleTo, I am unsure how I would go about using it in the case of dynamically generated assemblies. Is this even possible?
For one of my projects, I need to generate at run time some classes, and I thought it would be fairly simple to do using Reflection.Emit, but I'm getting MemberAccessExceptions when I run some of the generated code that calls methods that are marked internal in the generator assembly. Is there any way to tell the runtime that the dynamic assembly should be able to access my own code directly? I would really rather not publicly expose any of these members to consumers of my library.
Regarding InternalsVisibleTo, I am unsure how I would go about using it in the case of dynamically generated assemblies. Is this even possible?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
InternalsVisibleTo的工作原理是向其他人打开程序集。 因此，如果您想使用生成类型中的程序集Foo，则必须在AssemblyInfo.cs中为Foo指定生成的程序集的名称。如果您使用
AssemblyBuilder类生成新程序集，则可以指定生成的程序集的名称。 此名称必须与程序集Foo中的InternalsVisibleTo属性使用的名称相匹配。InternalsVisibleToworks by opening an assembly to others. So if you want to use assemblyFoofrom your generated types, you must specify the name of the generated assembly inAssemblyInfo.csforFoo.If you're emitting a new assembly using the
AssemblyBuilderclass, you can specify the name for the generated assembly. This name has to match the name used for theInternalsVisibleToattribute in assemblyFoo.我认为生成程序集中的成员被标记为内部是有原因的。
您可以在公共方法中公开必要的功能，或者只剩下两个选择：InternalsVisibleTo（如评论部分中提到的@tuinstoel）或反射（使用反射您可以访问不同程序集中的非公共成员）。
I suppose there's a reason behind the fact that the members in your generating assembly are marked internal.
You can either expose the necessary functionality in public methods, or you are left with only two choices: InternalsVisibleTo (as @tuinstoel mentioned in the comments section) or Reflection (using reflection you can access non public members in different assemblies).