Best Approach for testing VB DLL's during Design Time?
Posted on 2003-03-19
Perhaps I'm just missing something all together here. I'm developing a DLL in Visual Basic 6 to drive a data-driven website. As I develop the various classes of the model, I like to unit test each piece to be sure it functions as expected. The way I understand it, I have two options:
1. Build a VBForm based test app that references the compiled DLL, and write code against it to perform tests. When tests fail, go back to the DLL code, make changes, compile, and then go back to the test app. Problem here is I can't step into code and debug.
2. Build a VBForm based test app that includes each of the classes, so that I can test, step through code, make changes etc. until it works as desired.
Approach 2 works well enough I guess, except I have to have a seperate "tester" project setup, and I have to add to it all the classes I'm developing within my DLL project, and loading them into the tester EXE project changes their instancing properties, which I then have to change back when I open the DLL project back up etc..
Any thoughts? What's the best approach to being able to run and debug code in a DLL project as I work?