It might be that you're missing one of the dependencies from this OCX, you can use a tool like Dependency Walker to find what's missing. This seems to be a problem with the dataform.ocx ActiveX. Please let us know if you have any additional questions and please send an email to to get the pricing information. Even if you got 100% automation you still need to test the entire application because all the code is re-generated. You also need to take into account testing. Meaning 2%-5% of the lines will require some kind of manual change. Typical VB6 applications will have around 95-98% of automation. Normally you will require between 1/5 and 1/10th of the time it would require to do a manual rewrite. The manual effort will depend on the type of components used in the application. Our docs have some information of common issues and how to address them: ĥ.
This will depend on your application and how it is written. This might be because of unsupported components or changes between the platform. There will always be some manual work required to stabilize a migrated application. We can also offer some help with the remaining manual work if you need.Ĥ. The pricing will be based on the size of the application. Please send an email to to get specific pricing for your particular application. The license file itself will be tied to a particular application or set of applications.ģ. No, the VBUC is licensed per-application. This will depend on the things you use on your application.Ģ. Things such as remoting (when converting COM+ objects) or the VB compatibility libraries will not work there.Īlso, some third party libraries might not have. NET 5 don't have support for all the libraries and you might need some additional manual work. The recommendation is to go with the latest version of the Framework, however it is important to note that. MSDN: The license will let you migrate one application of up to 10,000 lines of code and put it into production.ġ. Hello, thanks for your interest in our tools.
0 kommentar(er)
