If you have linked ImageGear to your project using nuget, you can use the dotnet publish
command described here.
If you have linked ImageGear to your project using some other means, you will need to distriubte all dotnet assembly files that you are using in addition to any dependencies. See Assembly Dependencies.
Application Using PDF Component
In addition to what is packaged using NuGet, if your application uses the PDF component and runs on Windows, you also need to install the following Microsoft component:
- Visual C++ CRT 10.0
- Visual C++ CRT 12.0
This can be installed with the following merge modules:
- Microsoft_VC100_CRT_x86.msm (Windows 32-bit version)
- Microsoft_VC100_CRT_x64.msm (Windows 64-bit version)
- Microsoft_VC120_CRT_x86.msm (Windows 32-bit version)
- Microsoft_VC120_CRT_x64.msm (Windows 64-bit version)
If your application runs on Linux, you will need to specify the location from which native binaries will be loaded, otherwise ImageGear PDF will fail to initialize. You can do this by setting the LD_LIBRARY_PATH
variable to the location of native binaries before your application runs. If you linked ImageGear to your project using nuget, these binaries will likely be located at $(OutDir)/runtimes/linux-x64/native
.
See Also
Runtime Licensing