If you deploy a converted .NET executable on the end user’s computer and the application stops with an error stating that an ActiveX object or control can’t be created, check that the following conditions are all met:

1. If the application uses either of the following objects:
        Printer, Printers, Print or Print Setup common dialog, WinSock control
   then the VB.NET requires the VBSupportLib.dll COM component at runtime. At the end of the migration process this DLL is deployed in the Support DLLs folder; it should be copied to the end user’s computer and registered using the RegSvr32 utility.
2. If the application uses either of the following controls:   
        DataGrid, MSHFlexGrid, MSChar, MMControl, Calendar,
        Inet, MAPIMessage, MAPISession, MSComm, ScriptControl, Winsock
   then it is necessary that the corresponding OCX files be copied to the end user’s computer and registered using the RegSvr32 utility.
3. If the application uses COM+ services that have no managed counterpart in VB Migration Partner’s support library, you should ensure that the COMSVCS.DLL type library be copied to the end user’s computer and registered using the RegSvr32 utility.
4. Finally, you should ensure that all the type libraries used by the original VB6 projects and that haven’t been completely converted to .NET have been copied to the end user’s computer and registered using the RegSvr32 utility. For example, this is the case with the DAO.DLL and the ADODB type libraries.