Yea i know i\'m way behind times but what i\'ve got here is a antique VB6 editor app which i believe that no one will be upgrading to .NET soon. It uses a couple of third pa
I'm in the situation were we have a huge VB6 application which is on the way to be migrated to .NET. The migrated version is fully unit tested.
The approach we've taken is to unit test the VB6 application from .NET via COM interop. The main advantage we found so far is that VB6 developers end up learning TDD (and all what it implies):
This solution is improving hugely the code quality of the migrated version as they understand how to architecture things in a way that makes testing easier. Also, there's a potential opportunity to use the same tests on the VB6 and the .NET version.
Not sure if this solution is over-architectured for your problem. You should assess whether or not is applicable or suitable in your situation.
Regards.