[Progress Communities] [Progress OpenEdge ABL] Forum Post: .Net openclient usage in netstandard library (eg. from .net core)

  • Thread starter Thread starter dbeavon
  • Start date Start date
Status
Not open for further replies.
D

dbeavon

Guest
I was able to get quite far in my attempt to use the Progress "openclient" from a custom netstandard library. Unfortunately I haven't gotten past this error: Could not load type 'System.Data.OleDb.OleDbException' from assembly 'System.Data' . It happens when receiving results, after connecting to appserver (see InputTableStreamer.DoStreamResultSet in the namespace Progress.Open4GL.DynamicAPI). Netstandard libraries are supposed to allow us to put a dependency on any basic .Net framework assembly (that is compatible with the netstandard api). This only works as long as the assemblies aren't using any extremely unusual components (like OleDb). Based on what I can tell from reflecting on the Progress.o4glrt assembly there isn't a real good reason for the dependency on OleDb. It looks like there are a bunch of catch(OleDbException) blocks. They can be found all over the place but I can't imagine that any OleDbExceptions would ever be thrown. Would it be possible to get a version of the openclient assemblies for .Net that do NOT have references to OleDb? Or better yet, get a version that is compiled as a netstandard library instead of targeting the .Net framework? I was wondering if anyone else has ever attempted to use the .Net openclient from a netstandard library or on .net core. Hopefully Progress has future plans for the .Net openclient which will allow us to build apps that can be deployed outside of the .Net Framework. It would be very interesting to hear any news from Progress on this topic.

Continue reading...
 
Status
Not open for further replies.
Back
Top