As discussed before the solution is called Instant CloudMove while its main tool is called the Transposition Studio. Why transposition you probably ask yourself?! Well, we found that this term best describes what the tools do. Transposition refers to exchanging elements while everything else remains the same (in mathematics) or moving an element as is from one environment to another (in music). So how dows this relate to software and programming? Well, due to the award-winning Visual WebGui platform we are able to take the source code and put it in a modern technological environment with relatively few adjustments. As you can see in the diagram below Visual WebGui preserved the server centric architecture of client/server applications - enabling the same methodology of work by optimizing the message queue over the web:
Read the full post on ASP.NET Blogs:
Transposition - the success story of VB6 migration
We have already covered the BYOD requirements that an application developer is faced with, in an earlier blog entry (How to Bring Your Own Device (BYOD) to a .NET application). In that entry we emphasized the fact that application developers will need to prepare their applications for serving multiple types of devices on multiple platforms, ranging from the smallest mobile devices up to and beyond the largest desktop devices.
The experts prediction is that in the near future we will see that the majority of all applications developed, will need to be able to service these multiple platforms and devices in one way or the other, in order to survive.
Where does that leave our legacy single-platform targeted desktop applications, in which we have even invested decades of manpower?
We could build a User Interface front-end for those legacy applications, still running the legacy application as a back-end. That does in some cases require considerable effort, and it doesn't change the fact that the back-end is still running the legacy, and potentially obsoleted technology, code. On top of that, we will have two tiers to manage, the back-end and the new front-end.
We could rewrite or convert the legacy application for the new technology. For that there are multiple code conversion tools out there on the market that will assist you and make your conversion process a bit easier than to do it all "by hand". All the current tools in this category have one thing in common though, they do code conversion for you, and some of them even pretty well. You will still need to rewrite or reconstruct the parts of code where there is no corresponding library on the target platform.
We could migrate the legacy application to the new technology using any of the migration solutions available. The currently available solution base their migration on a fixed set of black-box built-in rules with no (or very limited) ability to adapt to your special migration needs. In many cases this will only help with the migration of a portion of your code, still requiring rewriting or reconstruction of considerable percentage of your code.
Taking on such a conversion or migration task means that you will use the code conversion/migration tool of your choice to convert/migrate your code. You will most likely have huge sections of code that need to be rewritten and/or reconstructed because there is no direct correspondence between the libraries used on the legacy application and the ones on your new platform. As soon as you start the conversion process, you will be converting the legacy application version that is current at that time, which can present major additional efforts in both management and coding if you need to continue maintaining the legacy application after you have started the conversion process.
What you really need here is a conversion tool that "knows" more about your legacy source application platform and the target platform and "knows" how to "map" between the two whenever possible. In addition, you often may need to continue development on the legacy application while you are converting/migrating. What you need is to lift that requirement and not freeze the development of the legacy application.
Based on these needs, Gizmox's built its solution and called the action transposition rather than migration or conversion. The Transposition studio is a rule based migration and modernization solution. It comes with built-in rules that will automatically handle about 95% of the conversion right out of the box. In some cases it will be able to migrate all your code. In other cases there will be portions that you need to work on yourself, but the entire work is done within the Transposition studio which is integrated into Visual Studio and offers you wizards and guiding tools to minimize risk and required resources.
What distinguishes the Transposition from other migration solutions are mainly three things:
First, it's migration rules are fully open and adjustable so you can change the default migration at will and thereby gradually adapting it to your own specific needs. It uses a very powerful pattern matching engine along with equally powerful template engine that enables you to make very advanced and complex conversions on small and large code segments, all by defining a set of rules and templates within the Transposition studio itself. The Transposition Studio integrates directly into the Visual Studio development environment and you have the legacy source code right at your fingertips and also allows you to override the defined rules by directly customizing parts of the code according to your needs. The rules and templates are stored in user definable libraries, where you can build multiple sets of related rules, which can then be used for, or shared with, other migration projects.
Second, there is no need to freeze development on the legacy source application, so you can continue developing your old application, while you are transposing. Using traditional migration/conversion procedures, you do a one time migration/conversion of the code, and then you start reconstructing/rewriting the parts of the outcome where necessary. This is completely different in Gizmox's Transposition studio. The majority of the required work is spent on defining migration rules and templates within the Transposition studio itself and then you simply re-run the transposition (migration) process to produce a new set of target code. You re-run the transposition as often as you need/like and it is only at the last stage, when you have migrated everything that can be migrated, that you start working directly on the target platform code.
Third, one of the target platform options is a cloud enabled and mobile enabled ASP.NET application with HTML5 frond end (based on the Visual WebGui framework) which will fulfill the BYOD requirement of modern applications perfectly.
I invite you to download and try the new Transposition Studio from Gizmox on a demo application.
It also presents a case where a large company converted an old Windows CE application into a web-based mobile application with HTML5 front-end. This allowed the company to upgrade the UI and freed them from the limitation to a certain mobile platform, so now they can use any Smatphone and Tablet they want.
We apologize for the delay in the release of those most expected versions, but we believe that the extra time lead to a more mature and complete product. As you can see the changelog is pretty long and includes a list of enhancements, new features and bug fixes: http://visualwebgui.com/Developers/KB/tabid/654/article/w_changelogs/Default.aspx
The new versions are available for all versions with open sources for Visual Studio 2005, 2008 and 2010.
You are welcome to download the WINWEB Free Trial and the Free .NETHTML5 beta on the downloads page.
Original post: New Enhanced Visual WebGui WINWEB and .NETHTML5 Versions
Application Migration: Windows/VB6 Apps to ASP.NET HTML5
The webinar is free and it will will introduce the substantial changes brought on by the move to Web Applications and Open Web architectures, and the challenges it places on application development shops. We’ll also introduce how we at Gizmox are helping client navigate this mobile shift and evolve existing Windows applications with a new set of Transposition tools called Instant CloudMove.
We will discuss the alternatives in the market to evolve your existing applications and focus on our transposition tools that reduce migration risk, minimize costs, and accelerate your time to market.
So if you have locally installed Windows, VB6 or ASP applications that you are looking to enable as SaaS, offer over private or public Cloud platforms or allow end users with mobile accessibility then you shouldn't miss this webinar.
Extending Windows Applications to HTML5 and Mobile Has Never Been Easier
Tuesday, April 24, 2012 1:00 PM - 2:00 PM EST
The new framework is optimized for enterprise mobility and supports the Bring Your Own Device (BYOD) trend. It produces totally secured cross platform and cross device HTML5 applications that doesn't bring or hold any data on the device (the entire logic and data stays behind the Firewall) and doesn’t require strong local computing resources. It also provides a native mobile user experience such as gestures. On the roadmap are utilization of local device resources via PhoneGap (open source) integration and Citrix receiver, along with Form Factor and Device awareness.
The current preview version provides limited functionality and capabilities and includes about 14 controls which were adapted for mobile requirements in terms of performance and user experience. Currently, the framework supports iOS and Android devices or Chrome and Safari and offers only one out-of-the-box theme - iOS like, but it is possible to customize it or create other themes as well. Upcoming versions will offer more capabilities including an HTML5 off-line feature that will ensure application availability even when there is no internet/network connectivity. We encourage you to download and "play" around with this version and will deeply appreciate your feedback. There is also a live HTML5 mobile mail application that was developed with the framework and available for browsing from mobile devices via this url:
Click here to Download the free preview and more info.
A Windows healthcare application for clinics and physicians needed a cost-effective way to accommodate all operating systems without reducing the existing functionality and security. Since users use a variety of operating systems, it was determined that a web-based version of the application was the best way to overcome those installation roadblocks. This was also a great opportunity to enable tablet access as well and reach users who use tablets such as the iPad for work.
A solution to turn this local Windows application to a cross-platform web-based solution was needed. It was important to complete the migration without having to manually rewrite the application and with minimal changes and resources involved. Running some assessment tools on the existing application provided estimations that almost 98% of the code could be automatically migrated into rich ASP.NET using the Instant CloudMove tools. “When we received the project estimations from the migration experts at Gizmox we were a bit skeptical at first as it seemed too good to be true” said Dr. Wendy Graham, Mihealth CEO and added “not only that the solution was exactly what we needed but it was also priced lower than all other alternatives.”
Those optimistic estimations turned into reality very quickly as the code migration was completed by Gizmox in only a couple of weeks. Then, in less than 2 months the entire project was completed and the migrated web-based physician tool was ready for delivery.
The final product was a completely identical version to the Windows application, with all of the functionalities, appearance, and feel, but was available through a web-browser from anywhere in the world. This allowed Mihealth to reach all clinics/physicians without turning away any potential customers. Implementation of mihealth™ also became much easier, as sales representatives did not face any of the previous complications when installing the application in a busy clinic on unfamiliar hardware or operating software. “Migrating mihealth to a web-based technology means we can now reach more customers with much less operative efforts and resources on our side. I can definitely say it made us more competitive” concluded Dr. Graham.
The original story was published here.