Jump to content


Mobilize.Net Staff
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About willvv

Recent Profile Visitors

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

  1. willvv

    Analyse Tool and 3Th Part Tools VB6

    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 sales@mobilize.net 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
  2. willvv

    VB6 to .NET POC

    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 info@mobilize.net or by phone at +1.425.609.8458. Regards, - Will
  3. 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.
  4. 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 --------------------------- What should I do? Yes or No?
  5. 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?
  6. 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 you a quote on each specific mapping. If the component is a "logic" library, it can still be used on the server side, bear in mind that the component will need to be registered on the web server and this might complicate the deployment process of the migrated Web application and it might be worth creating a mapping even if the component still works through COM Interop. Another thing to take into consideration when using COM components (and in general any external library on the server-side) is that once the application is migrated using WebMap, it will stop being a stateful application and become stateless. This means that if you had logic that created an object and kept it available for multiple user interactions, this behavior will have to be adapted to a stateless environment, creating some logic to re-create the components with each user interaction. Please let me know if you want more information and we can set a call to review your application and define the best strategies for your migration. - Will
  7. willvv

    How to improve the Overall Readiness of my app?

    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. Regarding creating your own custom packages, that is not possible at this point, but we would be happy to help you creating them for you and getting WebMap tailored to your specific application. Please contact us or reply to this post if you have additional questions about the customizations to WebMap.
  8. willvv

    What is a "custom package"?

    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.
  9. willvv

    errores email de confirmaciĆ³n

    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 added every week. In the case of your application, it seems that there are several libraries that aren't supported at this moment for your application. Even though some manual work is expected when you migrate any application using WebMap (some related to unsupported components and some due to differences in the platforms, things such as registry or filesystem access for example), we are allowing users with applications that have at least 80% of their PMEs supported by WebMap. If the support is lower than that we can still convert the application but we would like to have a session with the users to explain the results and discuss alternatives on those elements not supported automatically already. Please let us know if you still want to convert the application so we can set up a session with you. Regards, - Will

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