Is there a way in C# or .NET in general to create an attribute on a method which triggers an event when the method is invoked? Ideally, I would be able to run custom actions before and after the invocation of the method.
I mean something like this:
[TriggersMyCustomAction()] public void DoSomeStuff() { }
I am totally clueless how to do it or if it possible at all, but System.Diagnostic.ConditionalAttribute might do a similar thing in the background. I am not sure though.
EDIT: I forgot to mention that due to the circumstances of my specific case, performance is not really an issue.
This concept is used in MVC web applications.
The .NET Framework 4.x provides several attributes which trigger actions, e.g.: ExceptionFilterAttribute
(handling exceptions), AuthorizeAttribute
(handling authorization). Both are defined in System.Web.Http.Filters
.
You could for instance define your own authorization attribute as follows:
public class myAuthorizationAttribute : AuthorizeAttribute { protected override bool IsAuthorized(HttpActionContext actionContext) { // do any stuff here // it will be invoked when the decorated method is called if (CheckAuthorization(actionContext)) return true; // authorized else return false; // not authorized } }
Then, in your controller class you decorate the methods which are supposed to use your authorization as follows:
[myAuthorization] public HttpResponseMessage Post(string id) { // ... your code goes here response = new HttpResponseMessage(HttpStatusCode.OK); // return OK status return response; }
Whenever the Post
method is invoked, it will call the IsAuthorized
method inside the myAuthorization
Attribute before the code inside the Post
method is executed.
If you return false
in the IsAuthorized
method, you signal that authorization is not granted and the execution of the method Post
aborts.
To understand how this works, let's look into a different example: The ExceptionFilter
, which allows filtering exceptions by using attributes, the usage is similar as shown above for the AuthorizeAttribute
(you can find a more detailed description about its usage here).
To use it, derive the DivideByZeroExceptionFilter
class from the ExceptionFilterAttribute
as shown here, and override the method OnException
:
public class DivideByZeroExceptionFilter : ExceptionFilterAttribute { public override void OnException(HttpActionExecutedContext actionExecutedContext) { if (actionExecutedContext.Exception is DivideByZeroException) { actionExecutedContext.Response = new HttpResponseMessage() { Content = new StringContent("A DIV error occured within the application.", System.Text.Encoding.UTF8, "text/plain"), StatusCode = System.Net.HttpStatusCode.InternalServerError }; } } }
Then use the following demo code to trigger it:
[DivideByZeroExceptionFilter] public void Delete(int id) { // Just for demonstration purpose, it // causes the DivideByZeroExceptionFilter attribute to be triggered: throw new DivideByZeroException(); // (normally, you would have some code here that might throw // this exception if something goes wrong, and you want to make // sure it aborts properly in this case) }
Now that we know how it is used, we're mainly interested in the implementation. The following code is from the .NET Framework. It uses the interface IExceptionFilter
internally as a contract:
namespace System.Web.Http.Filters { public interface IExceptionFilter : IFilter { // Executes an asynchronous exception filter. // Returns: An asynchronous exception filter. Task ExecuteExceptionFilterAsync( HttpActionExecutedContext actionExecutedContext, CancellationToken cancellationToken); } }
The ExceptionFilterAttribute
itself is defined as follows:
namespace System.Web.Http.Filters { // Represents the attributes for the exception filter. [AttributeUsage(AttributeTargets.Class | AttributeTargets.Method, Inherited = true, AllowMultiple = true)] public abstract class ExceptionFilterAttribute : FilterAttribute, IExceptionFilter, IFilter { // Raises the exception event. // actionExecutedContext: The context for the action. public virtual void OnException( HttpActionExecutedContext actionExecutedContext) { } // Asynchronously executes the exception filter. // Returns: The result of the execution. Task IExceptionFilter.ExecuteExceptionFilterAsync( HttpActionExecutedContext actionExecutedContext, CancellationToken cancellationToken) { if (actionExecutedContext == null) { throw Error.ArgumentNull("actionExecutedContext"); } this.OnException(actionExecutedContext); return TaskHelpers.Completed(); } } }
Inside ExecuteExceptionFilterAsync
, the method OnException
is called. Because you have overridden it as shown earlier, the error can now be handled by your own code.
There is also a commercial product available as mentioned in OwenP's answer, PostSharp, which allows you to do that easily. Here is an example how you can do that with PostSharp. Note that there is an Express edition available which you can use for free even for commercial projects.
PostSharp Example (see the link above for full description):
public class CustomerService { [RetryOnException(MaxRetries = 5)] public void Save(Customer customer) { // Database or web-service call. } }
Here the attribute specifies that the Save
method is called up to 5 times if an exception occurs. The following code defines this custom attribute:
[PSerializable] public class RetryOnExceptionAttribute : MethodInterceptionAspect { public RetryOnExceptionAttribute() { this.MaxRetries = 3; } public int MaxRetries { get; set; } public override void OnInvoke(MethodInterceptionArgs args) { int retriesCounter = 0; while (true) { try { args.Proceed(); return; } catch (Exception e) { retriesCounter++; if (retriesCounter > this.MaxRetries) throw; Console.WriteLine( "Exception during attempt {0} of calling method {1}.{2}: {3}", retriesCounter, args.Method.DeclaringType, args.Method.Name, e.Message); } } } }
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With