willvv

Mobilize.Net Staff
  • Content count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About willvv

  1. 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?
  2. 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?
  3. 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
  4. 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.
  5. 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.
  6. 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