Frequently Asked Questions
Start here for the most common things our clients ask about our ASP.Net WebForms migration tool and services.
Reach out on the chat or our forums if you have additional questions.
Can I download a trial of the tool?
Short answer: Not yet.
Long answer: Our team specializes in creating tools to automatically convert legacy source code to new platforms. The WebMap to Angular migration tool is the latest addition to our toolset and it is based on our more mature WebMap tool.
The migration tools mature as our team adds support for new controls, libraries and code patterns.
The current version of the migration tool has support for a relatively small number of components and thus we cannot guarantee it will automate enough of your application out-of-the box.
This doesn't mean the tool cannot be used for your application, it just means that until we have added more coverage to the tool, we will need to be involved in the migration process and execute at least part of the migration for you.
How does it work?
This is not a trivial answer and we recommend you talk to one of our engineers to get a detailed explanation of the process and the architecture of the migrated application.
- We convert the markup to HTML and the WebForms tags to Angular components that use Kendo UI controls.
- We add event-handlers using TypeScript and send the events to the server.
- The server-side logic is kept on the server and the ASP.Net objects are replaced with C# models (POCO classes).
- We then use weaving to track changes to these models and serialize them to sync them with the client.
How much does it cost?
Since at this time we need to be involved at least partially in the process, the cost will be based on the size and complexity of your application as well as the current automation levels.
Contact us to talk to our sales team and get a quote.
Does it support VB.Net?
The main migration tool supports C# only, however we have another tool that can convert your VB.Net code to C#. We can use them together and migrate your VB.Net application to the new architecture.
Keep in mind that the migrated server-side code will be C# and not VB.Net.