Having been delving into the world of IoC, SoC and TDD, I find myself extracting an interface more and more often. A little too often… I have quite a few interfaces that exist as nothing more than a crutch. And now using AspView I have even more! Where will this madness end!
I know what you mean. I’m definitely guilty of interface-itis myself. But then again, I usually justify it by saying “interfaces are cheap”. But I can’t count the number of times that by having an interface for a particular class it has allowed me to extend the systems I work on and more closely follow OCP. And I don’t think that’s a bad thing.
I am still learning how to balance things a bit more to be a bit more pragmatic. Always learning… *sigh*
Joey BeninghoveAspView doesn’t *require* you to use interfaces. I’m assuming you are referring to TypedPropertyBag etc? You can still use Properties["username"] if you reallllly wanted to work with string literals and without intellisense.
Lee HensonOh I realise that Lee, but one of the reasons I did investigate AspView is because I wanted to use the strongly typed property bag. It’s swings and roundabouts really – there are up sides and down sides to this approach.
Colin Ramsay