Lets pretend that I have a class that has up to 5 external dependencies to be resolved by the DI container.
Some of the public class methods require 1 injected dependency, some require 5 injected dependencies. Is there a good methodology for avoiding injecting extra dependencies based on how the class is being used? So far I have just been using injection via class constructors and noticed how this might add some overhead during class construction. thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
