The project that I have the good fortune to have recently inherited is a right old can of worms.
Now, I hear you say, the benefits of a loosely coupled architecture are boundless and, when properly done, conduce to an easily implemented testing framework.
All well and good so far but, as a developer who has inherited a solution containing a gazillion factory classes, IoC container classes and interfaces I do have one small gripe.
It's a complete mess. Whereas in the days of yore we'd complain of spaghetti code we now seem to have spaghetti architecture. Try looking for the class you're after that implements a particular interface (and herein lies my question). Visual Studio has no feature to allow one to find all classes that implement a particular interface in the same way as one can find all references to a particular type.Is there some kind of tool/add-on available for this purpose? I hope so because all this not being able to see the wood for the trees nonsense is likely to drive old Buggeridge doolally over the coming months.
Now, I hear you say, the benefits of a loosely coupled architecture are boundless and, when properly done, conduce to an easily implemented testing framework.
All well and good so far but, as a developer who has inherited a solution containing a gazillion factory classes, IoC container classes and interfaces I do have one small gripe.
It's a complete mess. Whereas in the days of yore we'd complain of spaghetti code we now seem to have spaghetti architecture. Try looking for the class you're after that implements a particular interface (and herein lies my question). Visual Studio has no feature to allow one to find all classes that implement a particular interface in the same way as one can find all references to a particular type.Is there some kind of tool/add-on available for this purpose? I hope so because all this not being able to see the wood for the trees nonsense is likely to drive old Buggeridge doolally over the coming months.
Comment