Timeline for Logging without Code Bloat
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 28, 2015 at 14:35 | comment | added | user2023861 | @AndyBrush, The PostSharp people lock you in to their product and their product gets baked in to your code since it rewrites the MSIL. PostSharp was in vogue for a short time at my firm a few years ago. Now we want to move away from it because it hides functionality from non-expert users complicating development and maintenance. We're locked in however because so many users use the code. Any tech questions we send to PostSharp are quickly shot down because they don't support the version we use anymore. | |
| Mar 31, 2014 at 20:32 | vote | accept | Nick Williams | ||
| Mar 28, 2014 at 22:29 | comment | added | Scott Lerch | I've used Castle DynamicProxy to accomplish this in the past: docs.castleproject.org/… | |
| Mar 24, 2014 at 23:21 | comment | added | keshlam | I don't think we're actually calling it aspects, but we are applying something of that sort for the basics of our logging. There are certainly exceptions where we hand-code the logging instead, to better control what gets reported, but in many cases we do produce the entry/exit messages automatically. | |
| Mar 24, 2014 at 11:39 | comment | added | Andy Hunt | A good tool for this kind of thing is PostSharp | |
| Mar 24, 2014 at 10:32 | history | migrated | from programmers.stackexchange.com (revisions) | ||
| Mar 24, 2014 at 10:16 | comment | added | scheien | Aspect-Oriented Programming with the RealProxy Class is quite a good read. | |
| Mar 24, 2014 at 10:00 | history | answered | Bill Michell | CC BY-SA 3.0 |