We've been able to leverage binary compatibility to build interchangeable VB6 components housing code customized for individual customers so each customer could be distributed their own "version" of the component (ActiveX DLL). I'm in the process of migrating this application to VB.NET, and I'm looking for the same sort of functionality... Does anyone have any recommendations...? or does the elimination of "DLL Hell" effectively eliminate this sort of useful application of binary compatibility...? -- Ken Clark SunGard Investor Accounting Systems
