We started a discussion in the comments zone of the document http://communities.progress.com/pcom/docs/DOC-43828.
But I think it's better if I continue with it in a discussion.
I followed this guide (http://communities.progress.com/pcom/docs/DOC-6208) to install the OpenEdge MDG technology.
There's an update available of the .xml that describes the mapped objects on http://communities.progress.com/pcom/docs/DOC-43838.
Anyway, I also have problems with using it.
Schema imports are ok, but source code is very unstable. Some sources get imported, some don't. Even very simple procedures cause what seems to be an infinite loop...
One of the first things to mention is that when I start to import code, the .NET window (yes, the tool seems to be written in .NET) starts up with the error attached.
Is this perhaps related to the fact that I didn't install Visual Studio?
import source error.jpg
One of the first things to mention is that when I start to import code, the .NET window (yes, the tool seems to be written in .NET) starts up with the error attached.Is this perhaps related to the fact that I didn't install Visual Studio?
The fact that you are seeing this message indicates that you have the required .NET runtime installed. A Visual Studio should not be required. The error is a NullReferenceException. That translates to an invalid handle in the ABL (a classic coding error leading to a runtime error).
Seems like yet another reason why this tool should be provided with source code since then someone out here might fix it.
The code you are trying to import is OO code, no? What version?
Consulting in Model-Based Development, Transformation, and Object-Oriented Best Practice http://www.cintegrity.com
I was able to successfully register the 4 assemblies - but it does not solve the problem. I still see the "error - missing" in the Add-In Dialog of EA.
See attached screenshot.
I'm using the OpenEdgeMDGT.xml for 10.1A. The one from 10.2A doesn't show up nicely in the Resources view of EA.
The code I'm trying to import is a structured procedure with 2 internal procedures and 1 function.
Not a lot of action I would say...
as the error shows up before I start to import I doubt it is ABL related.
But, as you can see in the answer from Phillip Magnay, the tool will no longer support code-to-model engineering.
Isn't the reverse engineering stuff strictly OO?