It's all about letting client developers of your code add there own implementations. To do this your code needs to be very loosly coupled (i.e. none of the usual newing up of concrete classes, the code must be written using Interfaces for example) and configurable (e.g. the client developer drops their implementation dll into a location and adds content to a XML configuration file to tell your host app what class to load and instantiate from the dll).
This is a good intro to "Dependancy Injection" http://www.martinfowler.com/articles/injection.html
These are intros to Microsofts "Dependancy Injection" framework, Unity.
https://www106.livemeeting.com/cc/wwe_us/view?cn=guest&id=1032382093&pw=23D44136 with sourcecode at http://unity.codeplex.com/wikipage?title=Webcast%20demos&referringTitle=Home
http://visualstudiomagazine.com/articles/2011/01/27/the-factory-pattern-in-net-part-3.aspx
2 comments:
Finally I found what I was looking for.
How did you guys found this information? Thank you for your article I saw it on Google And I saved it. You have my email guys, so can you please send me an email when you post some new blogs on your site!!! Thank you and have a nice day. Regards - Web Application Development
Very good post.. this is what I am searching all around.
Thanks
--
DotNET Clubber
Your DotNET Clubber - Question and Answers
Post a Comment