Not sure if this is a known issue and whether there’s any way to avoid the below warnings when building MSI installer using VS2019?
------ Starting pre-build validation for project MyAddinSetup x64’ ------
WARNING: Unable to find dependency ‘ASPOSE.NOTE’ (Signature=‘716FCC553A201E56’ Version=‘22.3.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.IMAGING’ (Signature=‘716FCC553A201E56’ Version=‘22.5.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.CELLS’ (Signature=‘716FCC553A201E56’ Version=‘22.5.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.CAD’ (Signature=‘716FCC553A201E56’ Version=‘22.1.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.PSD’ (Signature=‘716FCC553A201E56’ Version=‘22.5.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.WORDS’ (Signature=‘716FCC553A201E56’ Version=‘22.3.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.EMAIL’ (Signature=‘716FCC553A201E56’ Version=‘22.4.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.BARCODE’ (Signature=‘716FCC553A201E56’ Version=‘22.4.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.ZIP’ (Signature=‘716FCC553A201E56’ Version=‘22.3.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.SLIDES’ (Signature=‘716FCC553A201E56’ Version=‘22.5.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.WORDS.SHAPING.HARFBUZZ’ (Signature=‘716FCC553A201E56’ Version=‘22.3.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.PDF’ (Signature=‘716FCC553A201E56’ Version=‘22.4.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.HTML’ (Signature=‘716FCC553A201E56’ Version=‘20.11.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.TASKS’ (Signature=‘716FCC553A201E56’ Version=‘22.5.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘NEWTONSOFT.JSON’ (Signature=‘30AD4FE6B2A6AEED’ Version=‘12.0.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.SVG’ (Signature=‘716FCC553A201E56’ Version=‘22.3.0.0’) of assembly ‘GroupDocs.Total.dll’
WARNING: Unable to find dependency ‘ASPOSE.DIAGRAM’ (Signature=‘DFDBA7CE0555EA8B’ Version=‘22.5.0.0’) of assembly ‘GroupDocs.Total.dll’
------ Pre-build validation for project ‘MyAddinSetup x64’ completed ------
@jarrodwee
Please share following details:
- GroupDocs API/DLL version
- OS details
- Sample application or a screencast/short video explaining the steps to reproduce the issue
Latest GroupDocs.Total.DLL v22.7.0.
Windows 10 Pro
Steps to repro in VS2019:
- Create simple application which uses the above DLL.
- Create MSI Setup Installer Project for installing the above application.
- Build the MSI Installer.
- You will encounter the warnings “Unable to find dependency” warnings.
Now, under the “Detected Dependencies” section of the Setup Project, if you right click on the GroupDocs.Total.dll and select “Dependencies”, it will show the following which should be equivalent to the warnings:
image.png (6.4 KB)
@jarrodwee
This warning is a known issue. But they don’t prevent from building a valid MSI installer package. However, we’ll further investigate this scenario and try to fix it. Your investigation ticket ID is GRPDOCSTOTAL-1.
@jarrodwee
Unable to reproduce the issue with the latest API version 24.1. Please use this console application -
ConsoleApp.zip (5.4 KB).
Forgot to mention that these warnings are for .NET Framework 4.8 project.
Issue is still reproducible using the latest GroupDocs.Total.NETFramework 24.3.
Attached herewith console app which reproduces the issue:
NETFrameworkGroupDocs.zip (36.6 KB)
Noted also that the original GroupDocs.Total package has been split into two separate .NET Standard and .NET Framework platform packages from 23.10 onwards.
Thought I’ll leave a note here in case it helps anyone else using .NET Framework and notice that there are suddenly lots more DLL dependencies from 23.10 onwards:
Important Note: Starting from 23.10.0, the GroupDocs.Total package has been split into two distinct platform packages: .NET Standard and .NET Framework . The GroupDocs.Total package is specifically designed to support the .NET Standard platform, making it compatible with .NET Core, .NET 5, .NET 6, etc. It includes backward compatibility improvements, allowing it to function with .NET Framework versions starting from 4.6.2. In addition, we have introduced the GroupDocs.Total.NETFramework package, which is optimized to run seamlessly in the .NET Framework runtime because it includes all the GroupDocs product libraries in their respective .NET Framework versions. It is tailored specifically for .NET Framework users and offers better dependency resolution for those utilizing the .NET Framework.
1 Like
@jarrodwee
We are conducting a more in-depth examination of this case and we value your input.
@jarrodwee
Unfortunately, we can’t fix this issue as these are package dependencies that are included into assembly. It seems that tool is expecting dependencies to be located in the same folder with the main DLL.
Okay, noted - thanks for the update.