public partial class Employee {

 

   public class NestedPropertyInterceptors {
       [BeforeGet(EntityPropertyNames.LastName)]
       public static void BeforeGetLastName(IPropertyInterceptorArgs args) {
          var emp = args.Instance as Employee;
          Console.Writeline("emp:BeforeGetLastName");
       }
    }

}

 

You can also define interception methods in a separate class, being sure to provide the TargetType of the interceptor, and then call the DiscoverInterceptorsFromAttributes method of the PropertyInterceptorManager to force discovery, like this:

 

PropertyInterceptorManager.CurrentInstance.DiscoverInterceptorsFromAttributes(

          typeof(EmployeeInterceptorExtensions));

 

    public class EmployeeInterceptorExtensions {

 

        [BeforeSet( Employee.EntityPropertyNames.Country, TargetType=typeof(Employee))]
        public static void LowercaseCountry(IPropertyInterceptorArgs<Employee, String> args) {
           var country = args.Value;
           if (!String.IsNullOrEmpty(country)) {
             args.Value = country.ToLower();
           }
        }
    }

 

I have one follow on question regarding Property Interceptors.  It appears that any method defined as a Property Interceptor must have public scope.  When I tried private and internal the method never executes.  While it's not a huge problem to have these methods be public, it really dirties up Intellisense.

 

I've tried using the System.ComponentModel attribute: [EditorBrowsable(EditorBrowsableState.Never)] but it still does not hide the method from displaying in Intellisense.

 

The only other 'solution' I could find to the problem was to prefix all of my Property Interceptors with an underline "_", to force them to move out of the way in Intellisense, but this is more of a hack than a real solution, and they're still visible in Intellisense, they're just not mixed in with real properties and methods.

 

Do you have a workaround for this?

 

Thanks,

Ken

 

You're not doing anything wrong.  We didn't get the documentation completely synchronized with the current functionality, and as you've found still have some old information.  We'll fix this ASAP.

 

In version 4.3.0 the get/set interceptors are always available and not controlled via the Object Mapper.  See the new chapter on Property Interceptors in the Dev Guide for information on how to use them.