There are few customers who are using VSFlexgrid 7.0 in their old legacy VB 6.0 applications, and want to migrate to the corresponding .NET version i.e. C1FlexGridClassic.
As C1FlexGridClassic derives from C1FlexGrid and provides an object model that is virtually 100% identical to the VSFlexGrid ActiveX control, allowing easy migration to .NET. Thereafter one can move to powerful, full-featured grid control, C1FlexGrid for .Net. This blog explains to the conversion of VSFLex 7.0 to C1FlexGridClassic. It can be achieved in two main steps: v7 to v8 and then v8 to .Net.
The first step is to convert from v7 to v8 of the VSFlexGrid. There is a Convert utility which is designed for conversion of applications based on VB6, so unfortunately it will not do anything for .NET applications. There were not many changes between VSFlexGrid 7 and VSFlexGrid 8, so a manual upgrade also is fairly easy. Following are the steps for the conversion:
If the application rebuilds successfully then the conversion from v7 to v8 is complete.
Now for conversion of application to .Net do the following:
This would transfer all your output to the new C1FlexGridClassic; however any design time properties would be lost so you have to make sure to take care of them by replacing the same in the Designer.vb or Designer.cs file. Usually the ActiveX runtime license appears to be added to the resources of the form to which it is added. Specifically, it is embedded somewhere in the Form.resx file, and is marked as OcxState for the control. This contains properties and apparently the license. (In case of VB 6.0 or VS.NET). In case you face some license problems then you may just delete the OcxState property in the Form.resx file and then load the project, recompile it and it would recreate the Form.resx-file. This would clarify a majority of things that you would need to migrate, and your project would be using the C1FlexGridClassic as of now in .NET environment. Hence the application is converted to .Net.