Home/ Questions/Q 651165
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T22:07:59+00:00

This is pretty much a duplicate question but instead of using Castle Dynamic Proxy

  • 0

This is pretty much a duplicate question but instead of using Castle Dynamic Proxy I’m using LinFu Getting underlying type of a proxy object

I’m using automapper to create proxies of interfaces that I’m sending to my viewmodel in Asp.net MVC. My problem is from what I can tell that MVC’s default MetadataProvider find the properties and metadata by calling .GetType() on the model.

So what happens is EditorFor() and DisplayFor() templates don’t generate any fields. What I need to do is find the proxy target type and then generate my templates. I know I can just parse the name and use GetType( “thename” ) but was wondering if there was an easy way.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    LinFu.DynamicProxy doesn’t directly expose the underlying object of a proxy. It simply redirects each method call to an IInterceptor implementation instance. In order to access the underlying object, you’ll have to figure out whether or not the current interceptor instance actually has a target class instance, or not.

    If you’re working with AutoMapper, AFAIK, they use LinFu.DynamicObject to do a lot of the duck taping, and calling GetType() on a dynamic type generated by LinFu.DynamicObject won’t even get you the actual type in your domain model–it will just get you an object that has been literally duck-taped together by LinFu itself.

    • 0