As I keep doing this on MVC projects, thought I may as well blog it, so the next time I need it I can find it myself :) To keep ASP.NET MVC controllers clean and organised, I find it much easier to split them so they handle only a single action each. This helps significantly with maintaining some semblance...
UPDATE: This facility made its way into Castle Microkernel, with name OnCreateFacility. I also made it possible to specify more than one actions. In one of Joshua Flanagan's recent post he mentioned about how they handle application configuration and I have to say that I liked their way. I also liked...
I don't want to be a wet blanket, but someone's got to put a stop to the IoC love fest going on out there. An Inversion of Control (IoC) container , for those of you were aren't yet familiar, allows you to retrieve instances of objects at runtime. A relatively common solution to a common...
Shhh...don't tell anyone but we don't unit test all of our code. We're striving to get all developers and managers on board with unit testing but we're not there yet. Despite our delinquency in writing tests one thing we do try our very best to do is keep mistakes from happening...
Posted to
Tim Barcz
by
Tim Barcz
on 11-14-2008
Filed under: Testing, Castle Project, Windsor, Tips And Tricks
Windsor will stitch together objects for you at runtime based on what components have been registered. When you ask for an instance of an object from the Windsor/MicroKernel it will return the object using the constructor it can satisfy. I ran into a problem the other day when I wanted to create...