D
dbeavon
Guest
Have you ever tried just attaching the VS debugger to a process running that .Net code and examine everything (ie. callstacks and memory)? I would guess that you could learn quite a lot. And then you could post whatever you wanted because you discovered it all independently 
. You might also try using the Progress/Telerik JustDecompile to open any interesting .Net assemblies that aren't part of the Framework itself. I would guess they are not going to be obfuscated, and you would probably be able to make some sense of it . That depends on what you are looking for. The integration is probably comparable to how progress integrates with java. For example, with the progress "JMS adapter" you can send and receive messages to a remote JMS-compliant broker. I think Progress launches a "symbiont" java process on the local machine and interacts with it via IPC. In truth they probably don't WANT anyone to have the underlying details about how it works. It is easier to change the implementation details when nobody else needs to be in the loop. The integration with the .Net bridge is probably even more efficient, than how they integrate with java. They can probably launch a .Net appdomain within the same process. It will be interesting to see how they decide to integrate with .Net core one day. While I am a .Net developer myself, I haven't ever used it from ABL because our OE installations have always been running on HP-UX. That will change soon, since HP-UX is end-of-life and OE 12 won't be certified on that platform anymore.
Continue reading...
. You might also try using the Progress/Telerik JustDecompile to open any interesting .Net assemblies that aren't part of the Framework itself. I would guess they are not going to be obfuscated, and you would probably be able to make some sense of it . That depends on what you are looking for. The integration is probably comparable to how progress integrates with java. For example, with the progress "JMS adapter" you can send and receive messages to a remote JMS-compliant broker. I think Progress launches a "symbiont" java process on the local machine and interacts with it via IPC. In truth they probably don't WANT anyone to have the underlying details about how it works. It is easier to change the implementation details when nobody else needs to be in the loop. The integration with the .Net bridge is probably even more efficient, than how they integrate with java. They can probably launch a .Net appdomain within the same process. It will be interesting to see how they decide to integrate with .Net core one day. While I am a .Net developer myself, I haven't ever used it from ABL because our OE installations have always been running on HP-UX. That will change soon, since HP-UX is end-of-life and OE 12 won't be certified on that platform anymore.Continue reading...