Hello Team - I am trying to get this to work within a workflow and am having issues with the DLL and compatibility. Does anyone have ClosedXML working within a workflow? We seem to have almost everything in order, but we are getting conflicts with dependent DLLs and it does not work. From what i have discovered, it is suggested that the conflict is occuring within the base dlls or GAC of the workflow server, so I am reluctant to alter those. We have set up everything from a script perspective, and have no conflicts using correct versions of dlls, however when we run the actual workflow, we get the conflict error. Any help is greatly appreciated.
Question
Question
Using ClosedXML to produce excel reports via workflows
Replies
Hello,
Closedxml requires a lot of dependencies to function.
Using it directly from a workflow may not be the right solution.
For my projects that need to use Closedxml, iTextSharp, or other files, I create custom activities that have the advantage of locating all the binaries in the same folder.
When the custom activity is created (.dll), a configuration file (.dll.config) is associated with it, which contains the dependencies used.
Regarding the GAG, I strongly advise against registering your DLLs there. It's dangerous and unmaintainable.
Hello Samir,
We came up with a solution that is using all tightly referenced versions of the necessary DLL and it is working when we have a hardcoded set of sample values to represent whjat should be the results of our Query token objects. This pulls the formatted excel and produces the needed spreadsheet, however, when we enable the token processing logic, we get null exceptions. Can you shine some light on what is needed to pass in the query tokens into such a script? I will share more specific information shortly.