D
dbeavon
Guest
XML could work. Or JSON too, which seems to be about 3x faster when I tested last. I'm assuming you are talking about using the CLR bridge? And you probably prefer doing it in memory rather than sending data to the file system and back? You may want to check out Tom Bergman's presentation at pugchallenge.org/downloads2017.html It is titled ".Net, Not Gui For .Net ". As I recall, it had some of the best examples I had found for moving datasets between ABL and ADO.Net. I think he used JSON, MEMPTR, and LONGCHAR. It is pretty fast, especially if you are serializing from the Progress side and deserializing on the .Net side. The other way around is not terrible either. On the .Net side there will be a dependency on Newtonsoft.
Continue reading...
Continue reading...