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.

What is the best migration strategy if the VB6 applications uses a lot of ActiveX controls?

April 26, 2017ActiveX applications best controls migration strategy uses vb6

0

10 Posted

What is the best migration strategy if the VB6 applications uses *a lot* of ActiveX controls?

1 Answer

0

10 Posted

• VB Migration Partner replaces a 3rd-party ActiveX control with a placeholder control (a picturebox control with red background); for obvious reasons the tool can’t correctly migrate references to the control’s properties and methods. To complete the migration process, you can choose among three different strategies. • If the control is used sparingly, it makes sense to migrate the application and then manually replace placeholder controls with the .NET control that more closely resemble the original ActiveX control. This strategy delivers a “native” .NET Framework application, but doesn’t support the convert-test-fix methodology. (In other words, your manual fixes are lost if you re-convert the application.) • You can use the AxWrapperGen tool to generate a .NET control that wraps the original ActiveX control. VB Migration Partner then uses the .NET control to replace all occurrences of the ActiveX control. This approach does support the convert-test-fix cycle, but delivers a .NET Fr