Jump to content


Mobilize.Net Staff
  • Content Count

  • Joined

  • Last visited

Everything posted by willvv

  1. 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.
  2. 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
  3. 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 lo
  4. 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
  5. 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.
  6. 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
  7. 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
  8. 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 migrati
  9. 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
  10. 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 applicati
  11. I just migrated an application and downloaded the code, I'm using VS2015. After I migrated the application (using Bootstrap+Angular) I opened it in Visual Studio and this error showed up: --------------------------- Upgrade project's Tools Version? --------------------------- Your project uses a version of TypeScript older than the version currently installed with Visual Studio. You may get errors if you try to build your project. Would you like us to upgrade the TypeScriptToolsVersion in your project file so you don't see this warning again? --------------------------- Yes No -------
  12. If I download the assessment for a solution from the studio, it doesn't have the information about Yellow/Green/Red PMEs, is there any way to do that besides copy&paste on the popup?
  13. It really depends on the type of component and whether it is already supported by WebMap. You can verify if a specific component is supported by reviewing the "Overall Readiness" chart when you upload the assessment for the project you want to migrate. If the component members (Properties, Methods and Events) are displayed in the red or yellow categories, they are not yet supported. For visual components, they will need to have an existing "mapping" to an equivalent HTML component. This can be done by Mobilize.Net's team through a customization to the tool, you will need to contact us to give
  14. Hi isanabria, thanks for your interest in WebMap. Here's a blog post explaining what the application readiness is and how to get in contact with us to migrate your application even if the readiness is low by letting us customize WebMap to generate the best possible code for your application. http://www.mobilize.net/blog/webmap-what-happens-if-my-application-readiness-is-low In general we don't recommend modifying the source application just to get it ready for a migration, this adds a lot of work to our clients and it can introduce bugs to the source application that will be hard to track. Re
  15. Hello ldfallas, thanks for your interest in WebMap. Here's a blog post explaining what the application readiness is and how to get in contact with us to migrate your application even if the readiness is low by letting us customize WebMap to generate the best possible code for your application. http://www.mobilize.net/blog/webmap-what-happens-if-my-application-readiness-is-low Please contact us or reply to this post if you have additional questions about the Custom Package.
  16. Hi mdiazg, thanks for your interest in WebMap. As you can imagine, the number of different components used by .NET WinForms applications is huge. In order to convert a component from WinForms to HTML5 using a modern web architecture (which is the main goal of WebMap) we need to create different "mappings" for each component, these mappings will define how each one of the Properties, Methods and Events (PMEs) of the components is generated in the Web application. WebMap has support for the most commonly used WinForms components (both Microsoft and 3rd Party components), and more mappings are a
  • 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