How do I convert an application from abal++ to ASP.NET application

Question

1.00/5 (1 vote)

See more:

I have an application written in abal++. Due to convenience we would like to convert it into ASP.NET.
Aside rewriting the whole program, is there any other options available to convert the app to ASP.NET without rewriting the whole app.

Thanks for your help.

Denisky.

What I have tried:

All effort proved futile. The only way out suggested to us is to rewrite the whole program.

Posted 28-Jan-22 1:13am

denisky

Updated 28-Jan-22 2:30am

Add a Solution

Comments

_Asif_ 28-Jan-22 7:31am

what is abal++?

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Dave Kreskowiak · Answer 1 · 2022-01-28T01:47:00

Solution 1

No. The only option you have to is rewrite the entire app.

Posted 28-Jan-22 1:47am

Dave Kreskowiak

OriginalGriff · Answer 2 · 2022-01-28T02:30:00

Abal++ is not available for .NET, so you really have no option but to rewrite the whole app. Even if there was a "direct conversion", what you would end up with would not be "good code" in the target language – they are based on very different frameworks, and what makes something work in one language does not always "translate" directly into another.
So what you end up with is very poor code, that is difficult if not impossible to maintain, that can’t be upgraded nicely, and that will cause you immense headaches if the original is changed. And it'll be a nightmare to debug if it doesn’t work "straight out of the box".
Instead, use the source code as a specification for a new app written in and for the target language / framework and write it from scratch using the original as a "template". You will get a much, much better result that will save you a lot of time in the long run.