Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Do converted .NET applications depend on Visual Basic 6 runtime?

April 26, 2017applications converted depend runtime visual basic

0

Posted

Do converted .NET applications depend on Visual Basic 6 runtime?

1 Answer

0

Posted

• No, with one minor exceptions: VB6 applications that use the Printer object, the Print common dialog, or the Winsock control do require a small component written in VB6, which in turn requires that the Visual Basic 6 runtime be installed on the end user’s computer. You can get rid of such dependency by implementing printing and winsock support by means of .NET Framework native classes and methods. If you never use the Printer.hDC property, however, you can easily modify the generated VB.NET app so that it uses the Printer object exposed by Microsoft’s VB Power Pack library, and you can use the standard Printer dialog that comes with .NET. Therefore, unless you use the Printer.hDC property, in practice the generated VB.NET project has a dependency on the VB6 runtime only if it references the Winsock control.