Question ClosedXML .net library | Can't view class object in Progress Developer Studio

JamesBowen

JamesBowen

19+ years progress programming and still learning.
I'm looking at replacing the COM Automation of using MS Excel and using the ClosedXML. .net library.

It looks like is going to do everything I need but I just can seem to get to all the listed namespaces, properties and methods in the class browser.

Is the some sort of hidden trick when using the Progress Developer Studio when viewing .net libraries?

ref:
github.com

GitHub - ClosedXML/ClosedXML: ClosedXML is a .NET library for reading, manipulating and writing Excel 2007+ (.xlsx, .xlsm) files. It aims to provide an intuitive and user-friendly interface to dealing with the underlying OpenXML API.

ClosedXML is a .NET library for reading, manipulating and writing Excel 2007+ (.xlsx, .xlsm) files. It aims to provide an intuitive and user-friendly interface to dealing with the underlying OpenXM...
github.com github.com
www.nuget.org

ClosedXML 0.105.0

See release notes https://github.com/ClosedXML/ClosedXML/releases/tag/0.105.0 ClosedXML is a .NET library for reading, manipulating and writing Excel 2007+ (.xlsx, .xlsm) files. It aims to provide an intuitive and user-friendly interface to dealing with the underlying OpenXML API.
www.nuget.org www.nuget.org
 
Just tried to test this and I am finding the exact same in that class browser is not listing anything.

I wondered if this was one of a few .NET components that Progress cannot access but it appears to not be the case:

Progress Customer Community

community.progress.com community.progress.com

I cannot explain why the namespaces, properties and methods are not being seen by class browser or the ABL.
 
Where do I place the start up parameter for -clrnetcore? is this a global startup parameter for Developer Studio, or for the project instance?
 
I have never used this parameter so not sure but based on this it looks to be a standard start-up parameter:

Progress Documentation

docs.progress.com docs.progress.com

As per the attached try setting for the relevant project.
 

Attachments

  • PDSOESTartupParameter.png
    PDSOESTartupParameter.png
    37.2 KB · Views: 5
Stupid question, but do I need to reference all the dependent .net assembly .dlls in the assemblies.xml?

I've noticed that if you install a package using nuget option, it will also install all the dependent .dlls as-well.
 
The majority of the time you just require the .NET DLL to be added to assemblies.xml and nothing else.

The only times I have experienced problems is if one of the following situations existed:
  1. The DLL was blocked so had to unblock.
  2. Access was required to another DLL and that DLL was missing. The DLL did not have to be added to assemblies.xml but had to be in the same folder as the main DLL. This is the situation you have noticed with the NuGet option as these would be the dependent DLL's that require access to but are not required to be in assemblies.xml.
However, if there are multiple DLL's then you could try adding them all to assemblies.xml - or at least ensure they exist in the same folder - to see if that solves.
 
You must log in or register to reply here.
Back
Top