If you want to get off VB6 we can offer you two choices:
We can start by giving you a "ballpark" estimate of the costs of migrating your app, either if you want to use our tools to do it yourself or if you want us to execute the project for you.
The pricing of the project will depend on several factors, including the size of the application and the libraries used by it.
After you have the results from this assessment we can have a short call to gather some additional information about your migration goals and then we can prepare the "ballpark" estimate for you. This ballpark will give you the exact price of the license as well as some estimates for the (optional) services with a 25% margin of error.
Here are the steps you need to follow to run the VBUC in assessment mode (or watch this video):
The Visual Basic Upgrade Companion has a built in analyzer to understand your VB6 project. You can download a free trial of the VBUC here. Once you have completed the form, you will get an email with the download link and the trial license.
In addition to ensuring that the environment in which you’ve installed the VBUC can run your VB6 application, it’s important to place all of your VB6 source code under one directory. At which point, makes sure that it can compile and run properly. Any “test” projects or unused references would be best removed at this point.
Once your VB6 projects are ready, launch the VBUC. The application should start with the Solution tab already selected. In the workflow diagram on the left, note that this is step 1 of 5. If not, go there now. Click on the New icon to create a new VBUC solution. You’ll notice that the Upgrade Solution Properties form that pops up suggests a solution name of UpgradeSolution1. Please choose a name that best represents the application or suite of applications that is being assessed. Then select the source path of the VB6 source code. And output path will be suggested. Please remember this path as it where the assessment files will be placed. If any binary references are located outside of the source path, you may add additional binary reference folders so that the VBUC can best perform its dependency analysis. Click OK to create the solution.
After the solution has been created, go to the second step on the left, Resolve. VBUC lists references and unresolved CreateObject statements along with the binary folders specified in the previous step. A reference is resolved when there is a green check mark (unresolved references are flagged with a red “x”). Right-click on any reference that is not resolved and choose Set Reference Manually. Make sure that all references are properly registered before trying to add them. File extension types may include DLL, OCX, and TLB files.
If the red “X” does not change to a green check mark after setting the reference manually, you may want to try to force a refresh by going to the Solution tab and choosing the Refresh option.
If all references have been resolved correctly, the workflow step “Resolve” will have a green check mark next to it rather than a yellow caution triangle. While it is not necessary to resolve all issues in this step before proceeding to the next, the assessment will be more complete is all references have been resolved.
After creating the VBUC solution and resolving references, proceed to the tools tab. Find the Assessment icon shaped like a magnifying glass with a checkmark in it. Click the assessment icon.
Once completed the assessment will display a Show results button where you can preview the data that you will be sharing with us.
If you open Windows Explorer to the output path specified in first step when the VBUC solution was created, you will see the Assessment directory with all the generated files. The XML files contain information about project dependencies, line count data and other VB6 assessment data.
You will also see a ZIP file prefixed with the VBUC solution name. The ZIP file contains the elements in the Assessment directory ready to be sent to us.
Please share this information with your Mobilize.Net contact or with firstname.lastname@example.org and we will schedule a call to review the results and present you some estimates for the migration.