Jump to content


Mobilize.Net Staff
  • Posts

  • Joined

  • Last visited

About willvv

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

willvv's Achievements


Newbie (1/14)

  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges



  1. Hello Prasad, The licensing is done based on a total number of lines of code (i.e. if you have 5 applications of 10,000 lines of code you'll need a license for 50,000 lines of code). We can generate individual licenses for each application or we can generate a single one that lets you migrate all of the apps (at once or independently). We do suggest you migrate the apps that are related (when they have inter-dependencies or shared files) at once. This will ensure those internal references and shared files are generated correctly and prevent some extra work after the automatic migration. Please tell them to reach out to us at [email protected] - Will
  2. Hello Prasad, yes, the same VBUC can be used to convert classic ASP.
  3. Hello Prasad, Please reach out to us at [email protected] where we can assign you an account manager and a solutions architect that will help you with a license you can use in production and a support package that can help you complete the modernization successfully. - Will
  4. You're welcome. The current version of the VBUC doesn't have 4.8 as an option, but selecting 4.7.2 will not prevent you from using it. It will be updated once you open it in Visual Studio. - Will
  5. Hello, thanks for your interest in our tools. Let me try to address your questions: MSDN: The license will let you migrate one application of up to 10,000 lines of code and put it into production. 1. The recommendation is to go with the latest version of the Framework, however it is important to note that .NET Core / .NET 5 don't have support for all the libraries and you might need some additional manual work. Things such as remoting (when converting COM+ objects) or the VB compatibility libraries will not work there. Also, some third party libraries might not have .NET Core support. This will depend on the things you use on your application. 2. No, the VBUC is licensed per-application. The license file itself will be tied to a particular application or set of applications. 3. Please send an email to [email protected] to get specific pricing for your particular application. The pricing will be based on the size of the application. We can also offer some help with the remaining manual work if you need. 4. There will always be some manual work required to stabilize a migrated application. This might be because of unsupported components or changes between the platform. This will depend on your application and how it is written. Our docs have some information of common issues and how to address them: https://docs.mobilize.net/vbuc/issues-troubleshooting 5. Same answer as above. The manual effort will depend on the type of components used in the application. Normally you will require between 1/5 and 1/10th of the time it would require to do a manual rewrite. Typical VB6 applications will have around 95-98% of automation. Meaning 2%-5% of the lines will require some kind of manual change. You also need to take into account testing. Even if you got 100% automation you still need to test the entire application because all the code is re-generated. Please let us know if you have any additional questions and please send an email to [email protected] to get the pricing information. - Will
  6. This error is typically fixed by removing the StdType reference from the list of references in your project. Sometimes the migration process generates some unnecessary references to some DLLs that can be safely removed from the project.
  7. During the conversion, the VBUC will generate a Support project as part of the migration. This Support project will contain the stub methods generated by the tool as well as all the API calls which are extracted by the tool and centralized in a single project. The manual process of the migration should start by compiling the helper classes (if you included them as source) and then compiling the Support project. After this you can begin compiling the migrated projects (which will likely have a reference to the support project). I hope this helps. - Will
  8. Hi Dave, This seems to be a problem with the dataform.ocx ActiveX. 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. The best approach is to use the original installer for the particular component, it will end up registering all the dependencies correctly. This is one of the reasons why we suggest to execute the migration in the same development environment where you can compile your VB6 code. Now, if it's possible to replace this component you might end up in a better position, by no longer relying on an OCX. The strategy for this will depend on the controls you're using and how you're using them. We can also help with this strategy by creating tool customizations that will add rules to the tool so the migration of the component is automated. Let us know if you want to learn more about this option or if you need our team to help with part (or all) of your project.
  9. Hi Mindy, Whenever you have a reference like this, the best way to figure out what it refers to is by searching your registry for that GUID. This particular one shows as referencing the mscomctl.ocx ActiveX in my computer: You can also try with a Google search and if it's a known file you should find it easily. This is an uncommon issue and it typically happens if you try to run the migration in an environment different to the development environment (which is the recommendation). - Will
  10. willvv


    Hi Dan, The Get Free Trial button will submit your info and the licensing system will send you a couple of emails, one with the link to download the VBUC and another one with the trial license file as an attachment.
  11. willvv


    Hi Damian, We haven't seen many applications built using Borland Dev Studio, but C# Winforms is cenrtainly right up our alley so I don't see why we wouldn't be able to convert the code with our tools (we'll probably need some customizations in case Borland's file format differs from Visual Studio's). I'll send you a direct message to coordinate a call to explain our tools, methodology and next steps. - Will
  12. willvv

    Trial version

    Hello Arnaud, After reviewing our logs it seems that the problem was with the messaging because you had already downloaded a trial license last year. I just re-generated a new trial license and sent it to your email (using the address you submitted today). Now you should be able to download the license or use the one attached to the email. Please let us know if you have any other questions (and be sure to download the latest VBUC, version 8.1, it has lots of improvements!) Regards, - Will
  13. Hi Mark, sorry about the delay with the response. Here are the answers: - You can download the assessment tool from here: https://mobilize.blob.core.windows.net/clickonce/SFX/AssessmentWizard.zip, once you get the results you can share them with us at [email protected] so we can set up a call and review them with you to suggest next steps. - Our migration tools have support for several third party libraries and support for additional libraries is added frequently. At this point we don't support the Janusgrid component but we can certainly add support for it as part of a migration project, or if you want you can add support for it yourself after the migration project (by default the migration tool will create a placeholder on the client-side which can be implemented in a very straightforward way). Regarding the target library, we use Kendo UI for Angular components, however it is possible to extend this and use any other UI library that can be used with Angular 6. I hope this answers your questions. - Will
  14. Hello and thanks for your interest in our migration technology. There are several things that need to be done before migrating a VB6 application, including: - Completing a source dev environment. This should include all the source VB6 code and third party components. The code must compile and be debuggable, this is important both for the migration process and afterwards when you are performing manual changes to the migrated code to debug source and migrated applications side-by-side. - Defining the strategy for third party components. If there are libraries not supported by the VBUC they can either be used through COM Interop (some old components cannot be used this way), manually replaced by .NET equivalents or our team can customize the VBUC for you to automatically convert this component to another one in .NET (this is especially useful for elements used in many places). - Identifying the best set of migration options to make sure the migrated code is the best for your source VB6. This means executing the migration process a few times and comparing the results and the issues remaining in such code. - Once the code is migrated you can move it to a .NET environment as long as you have already registered any COM components that you will leave in the migrated application. Otherwise you might have problems compiling the application. This doesn't have to be a separate environment although most people prefer to do so. Our team can help you with all these steps and we even offer a quick start package that includes some on-site work with one of our migration architects to get you started without wasting any time. We can also execute part or all the project if you prefer so. Please don't hesitate to contact us at [email protected] or by phone at +1.425.609.8458. Regards, - Will
  15. Hi @wangw, thanks for choosing the VBUC to modernize your VB applications. References to the Office libraries (Word, Excel, Outlook, etc.) need to point to the automation object library file for the corresponding application, these files have the OLB extension. In the case of Word it is located in the path: c:\Program Files\Microsoft Office\[OFFICE VERSION]\MSWORD.OLB You can fix the reference by right-clicking on it in the VBUC and browsing for this path This type of errors with "unresolved references" can usually be avoided by making sure you have compiled your VB6 application in the environment where you have installed the VBUC. VB6 will let you know if there's a missing third party component that you need to install before executing the migration. Please let us know if this works.
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. Terms of Use