Monday, June 23, 2025

Updating the Novigo PDF Marketplace Component/Custom library in UiPath


Prerequisites:

·        Visual Studio (any edition supporting .NET Framework 4.7.2)

·        NuGet Package Explorer

·        dnSpy (or another .NET decompiler)

·        Access to the Novigo PDF activity’s source DLL and your UiPath project

Step 1: Install Visual Studio

·        Download & install Visual Studio from Microsoft’s site.

·        During setup, ensure “C# Windows Class Library (dll)” project is selected.

Step 2: Create a C# Class Library Project (Optional - Use only for new custom components)

·        In Visual Studio, File → New → Project.

·        Choose “Class Library (.NET Framework)”.

·        Name it something like CADMV.Navigo.PDF

 

A screenshot of a computer

AI-generated content may be incorrect.

Step 3: Target .NET Framework 4.7.2 (Optional - Use only for new custom components)

·        In the new project’s Properties → Application tab, set Target Framework to “.NET Framework 4.7.2”.

·        Save; this match UiPath’s supported runtime for custom libraries.

·        Add mandatory references System.Activities & System.ComponentModel.Composition.

A screenshot of a computer program

AI-generated content may be incorrect.

Add dependencies if needed

A screenshot of a computer program

AI-generated content may be incorrect.

 

A screenshot of a computer

AI-generated content may be incorrect.

Step 4: Decompile & Import the Original DLL

·        Open your existing Novigo PDF activity DLL in dnSpy.

·        Right-click → “Save Code” (or “Export to Project”) to get a starting .csproj using dnSpy tool.

·        Copy any helper classes or interfaces you need into your Visual Studio project.

Step 5: Update web.xml Hint Path

·        Locate web.xml in your activity’s Resources folder.

·        Find the <hintPath> element that points to the original System Activities package.

·        Change it to the path where UiPath now stores its system activities, for example:

A screenshot of a computer program

AI-generated content may be incorrect.

 

 

·        Save the file so your library will compile against the correct assembly.

Step 6: Add Custom DLL Dependencies

·        In NuGet Package Explorer, open your project’s package (or start a new one).

·        Go to the Dependencies section and click Add Dependency.

·        Browse to and select any custom DLLs your library relies on (e.g., itextSharp.dll).

A screenshot of a computer

AI-generated content may be incorrect.

·        Specify the version and target framework for each so they get bundled into the final .nupkg.

A screenshot of a computer

AI-generated content may be incorrect.

Step 7: Package with NuGet Package Explorer

·        In the Metadata tab, update: ID (e.g., CADMV.Navigo.PDF), Version (e.g., 2.1.0), Authors, Description, etc.

·        In the Files tab, include your compiled DLLs (both your custom library and any bundled dependencies), plus any license/readme.

·        Highlighted group target framework needs to be updated after updating the nuget

A screenshot of a computer program

AI-generated content may be incorrect.

 

<?xml version="1.0" encoding="utf-8"?>

<package xmlns="http://schemas.microsoft.com/packaging/2012/06/nuspec.xsd">

  <metadata>

    <id>Class3</id>

    <version>1.0.0</version>

    <title></title>

    <authors>mwvxs19</authors>

    <owners></owners>

    <requireLicenseAcceptance>false</requireLicenseAcceptance>

    <description>My package description.</description>

    <dependencies>

      <group targetFramework=".NETFramework4.7.2" />

      <group targetFramework="net8.0-windows7.0" />

    </dependencies>

  </metadata>

</package>

 

·        Save as a .nupkg.

 

Step 8: Deploy & Test

·        Copy the .nupkg into your local UiPath Packages folder (e.g., %UserProfile%\.nuget\packages).

·        In UiPath Studio: Manage Packages → Local, find your updated Novigo PDF package, and install it.

·        Build and run a small workflow to verify your changes work as expected.

·        When satisfied, push the .nupkg to your Orchestrator or the public Marketplace.

Tip:

Keep your assembly info, NuGet metadata, and dependency versions all in sync to avoid runtime mismatches.

No comments: