asp.net mvc 3 - Strategies for Organizing Dependencies/IOC Containers in an MVC3 .Net app with Castle Windsor -
So I'm new to using Castle Windsor and I became rather how ugly your controllers me your project the IOC, which has been found to work I'm most people is less than half the problems now announced a ton of dependency in your controller constructors I know that I'm down. Are there any good specimens to manage them, so I'm not copying / pasting it in every new controller and / or section of the site I created?
public Home Controller (Aiookelaijeshn service location service, // ugly events service, media server service Uttrsewa, Aitivitr Fds service Twitter service, Aiafsbuksewayrsewaisewaisej, Aistitingssewa Setingssewayr, Aiiakstainetdeta service Bahreedeta service, Aiyuesaars service Ugrsewa, Aiaianstent message service instant messaging service, the Aisiaelanders Karenjr Received, Iloggr logger) {// These are some things} to link I hope this makes sense. I can add more information for clarification.
It looks like your administrator or try to do too much of administrators to be more specific, so In fact, with the exception of general stuff like ilogger , they do not require much dependence. Review the action methods on controllers, and see who have the same behavior and dependencies - they are the candidates to go to their own controller.
Comments
Post a Comment