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 VB.NET applications require a support library?

April 26, 2017applications converted library require support VB.NET

0

Posted

Do converted VB.NET applications require a support library?

1 Answer

0

Posted

• All applications generated by VB Migration Partner require that the CodeArchitects.VBLibrary.dll file be deployed with the VB.NET executable. The support library is essential to support features that have no counterpart in VB.NET – control arrays and DataEnvironment classes, for example – or that are implemented in a completely different way (graphic methods or data binding, just to name a few). It should be noted that also applications converted with the Upgrade Wizard may require a companion library – more precisely, the Microsoft.VisualBasic.Compatibility.dll library – to support features such as control arrays, resource files, and a few controls that have no counterpart under VB.NET – namely, DriveListBox, DirListBox, and FileListBox. We just decided to improve on this concept and created a support library that can account for virtually all the VB6 features that VB.NET doesn’t support natively.