Borland C++ using OWL to MFC Migration

I have an application built entirely on Boralnd C++; uses
OWL extensively; also uses OCF.
1. How easy or difficult to migrate this code completely to MFC.
2. Are there any tools available?
3. Are there any other resources(Books, white-papers, etc) available.
Who is Participating?
winmeisterConnect With a Mentor Commented:
I am afraid you are making the same mistake I did last year. There is NO class mapping, there is NO general strategy.

You have to study MFC and hope that your application specific code can be pasted. As I said, the GUI code has to be re-writtem. Let's say, OWL's TWindow class is completely different from MFC's CWnd. You cannot just change the class name, but you have to re-write the code. MFC doesn't have the SetupWindow method, but it uses other ways to initialize the window.
seedyAuthor Commented:
Adjusted points to 200
I made such a job about six months ago. There is no tool or specific book available. You should have a good MFC book (there are many of them ). I had to rewrite the whole code, but the old OWL code was not completely useless; I have cut&pasted about 50% of the code.
You have to rewrite the GUI-specific code, but you can keep all your application-specific part of the program.
It can seem a huge work, but it isn't. Let's say: it's a challenge!
seedyAuthor Commented:
I instinctively knew these details.  What I was looking
for is pointers to more specific details like... may be a
class mapping between OWL and MFC, or some notes that describes
the strategy that should be used, etc.  I need more details.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.