If you need to use an outside package/library/assembly in a Workflow script (e.g., NuGet), how do you register that?

asked on September 19, 2023

I'm looking at an existing script that was written by a previous developer.

In the script itself it has several "using" statements:

namespace WorkflowActivity.Scripting.Script
{
    using System;
    using System.Collections.Generic;
    using System.ComponentModel;
    using System.Data;
    using System.Data.SqlClient;
    using System.Text;
    using System.Linq;
    using CsvHelper; // available on the web
    using ITS.Data; // custom for my company
    using System.ComponentModel.DataAnnotations;
...

A few of of these are not from Microsoft, one is available as open source through NuGet and one is developed by my own company.

What process needs to happen to allow Workflow to recognize package/library/assembly like this?

In Visual Studio, I would use a NuGet package manager to install packages

0 0

replied on September 20, 2023

Hi Kristi,

I wrote up instructions here: https://answers.laserfiche.com/questions/200906/Laserfiche-ability-to-configure-SSL-in-API-calls#201663

In short, for packages/libraries/assemblies on Nuget: "download the package directly from nuget.org, use 7zip to extract it, and copy the dll(s) to your .\Program Files\Laserfiche\Workflow installation folder."

For the library your company developed, similarly place the dll in the Workflow folder mentioned above.

Then in the Workflow script editor's left-hand bar, find the references list, right-click, and add the references by path. Then, assuming all dependencies can resolve as well, your using statement should work.

Hope that helps!

Cheers,
Sam

1 0

Question

Question

If you need to use an outside package/library/assembly in a Workflow script (e.g., NuGet), how do you register that?

Replies

Sign in to reply to this post.