Microsoft | patterns & practices | Developer Network | Enterprise Library | Acceptance Testing Guide | Personal Site
Last month we shipped the new versions of Microsoft Enterprise Library and Unity. They've been very well received. Today we are pleased to add the following guidance assets to enhance the set of reusable components:
As a reminder, we also have a Migration Guide, which we shipped earlier, to help you move your app from using EntLib v5 to v6.
We hope these additional materials will help you learn EntLib and Unity and get quickly up to speed in using them.
In p&p we consider the written guidance that complements our code to be as important as the code itself. We spend a lot of time and effort making sure that it’s technically accurate, as well as engaging to read. We appreciate your patience while we work on polishing and finalizing the developer’s guides and making them available as books (both printed and eBooks). We’ll gratefully accept your feedback on any of the above. We are also seeking EntLib and Unity users willing to share their stories as case studies to be included in the guides. If you are interested in contributing a short story, please contact me for details.
Happy learning, happy experimenting, happy coding!
@8 & 9: Unity and entlib reference documentation refers to the same link.
Thank you, Anders, for pointing this out. Fixed now.
When should I use ICallHandler or IInterceptionBehavior in new projects?
If you need to target specific methods with some flexibility you're better off using Policy Injection, which relies on call handlers. If you want to address crosscutting concerns for all methods of an intercepted object, or only some methods but with some fixed logic, behaviors are probably easier to use. Also, using PIAB's call handlers results in some overhead when all methods are scanned and the matching rules are applied to them.
So interceptions are better in performance, and call handlers are more flexible.