Reply to thread

Message: [QUOTE="Guest, post: 7805457"] Thanks, Randy. This will indeed work. But I must create test methods in each inheritor and decorate them with the [TestMethod] attribute. As you suggest, those test methods will call the parent where the interesting code can exist (at least we avoid duplicating that part, which would be tedious and error-prone. But I was hoping to avoid duplicating the method shells as well. If I'm going to do this, I don't even need inheritance, I can use composition. Anyway, when I add a new method to the interface, I have to add the complex logic once (good) but I have to create a shell method in every database implementation. A looping approach would allow me to create only one test method. thanks -- David K Allen Carlson School of Management University of Minnesota Minneapolis, MN : .... .... [/QUOTE]