D
dbeavon
Guest
Thanks for the links Laura and Evan. I did see the references to the Java openclient changes. But I didn't see anything about any .Net openclient changes. One day I still hope to be able to use the APSV openclient from ".Net Core". I suppose for now we could investigate switching over to SOAP or REST ... but it would be a substantial effort. From what I had seen (using Telerik decompiler) the effort to allow the .Net openclient to run on .Net Core is extremely minimal (ie. just remove some references to OLE DB exceptions). Maybe Progress should put the .Net openclient on github so we can do this ourselves? Whats new in OE 12 (lots of good stuff
docs.progress.com/.../New-in-OpenEdge-Release-12.0.html I was interested to see the OEM/OEE is being moved out of admin server framework. It confirms that, while possible, there are probably not many folks who want to use PASOE without an admin console. We've always been told that you could install it independently of adminserver for production deployments. But it seemed very impractical considering that you lose the GUI console and, without it, most Windows administrators would feel like they are operating in the dark. GUI's are fairly popular nowadays. 
Continue reading...
docs.progress.com/.../New-in-OpenEdge-Release-12.0.html I was interested to see the OEM/OEE is being moved out of admin server framework. It confirms that, while possible, there are probably not many folks who want to use PASOE without an admin console. We've always been told that you could install it independently of adminserver for production deployments. But it seemed very impractical considering that you lose the GUI console and, without it, most Windows administrators would feel like they are operating in the dark. GUI's are fairly popular nowadays. Continue reading...