Conclusion

Conclusion

Although the Upgrade Wizard makes life easier by having your upgraded Visual Basic 6 applications use the same ActiveX controls, keeping the ActiveX controls means that you do not reap any of the benefits of an application that is based 100 percent on .NET controls and components. Unfortunately, the Upgrade Wizard does not give you the choice of upgrading the ActiveX controls in your project to the equivalent Windows Forms controls.

This chapter has demonstrated how you can manually replace ActiveX controls with equivalent Windows Forms controls after your project has been upgraded. If the ActiveX control you need to replace has a flat object model, it is a relatively straightforward process to map its properties, methods, and events to those of the equivalent Windows Forms control. If, on the other hand, you want to replace an ActiveX control that has a rich object model with the equivalent Windows Forms control, you will need to restructure your code so that it fits the object model defined by the Windows Forms control.