I'm focused on developing and expanding my knowledge and skills. Enjoying new challenges. I'm assuming that there are no stupid questions, there are only silly answers.
Yes I've used LoggingInterceptor in production application. It's logging methods arguments and results. I haven't used MonitorinInterceptor in production because I've used dedicated profilers ex. Jetbrains dotTrace or profiler build in Azure.
I didn't face problems connected with AOP approach. Maybe my application isn't too big and that is the cause of that. I've used in my work postsharp when it was free. I used it in big scale application and it was working fine.
You asked about pitfalls. As I wrote in summary I've used AOP very carefully and didn't change methods results in an Interceptor.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi Rafal,
Have you ever use it in production application? What sort of pitfalls can you imagine?
Best regards
Hi Pawel.
Yes I've used LoggingInterceptor in production application. It's logging methods arguments and results. I haven't used MonitorinInterceptor in production because I've used dedicated profilers ex. Jetbrains dotTrace or profiler build in Azure.
I didn't face problems connected with AOP approach. Maybe my application isn't too big and that is the cause of that. I've used in my work postsharp when it was free. I used it in big scale application and it was working fine.
You asked about pitfalls. As I wrote in summary I've used AOP very carefully and didn't change methods results in an Interceptor.