Missing dll when deploying ClickOnce

Question

When I publish the ClickOnce application, one of the links that is included in one of my projects is missing.

If I go to my project Properties → Application Files, this missing link is not even listed here.

There is a .exe.manifest file in my bin / Release folder, and I noticed that it is also missing here.

However, when I create the project, the DLL is actually copied to my bin / Release folder.

How can I make sure that it also deploys this required dependency?

Answer 1

I finally found a solution to this problem, and I hope this solves your problem. In my case, I am editing an old application at work that has several projects, but the main project and its rear project are the most important here. The back part is added in the "Links" section of the main project. A third-party dll was imported on the back side, but another 2 dlls are required for this DLL. Thus, these 3 libraries were added in the "Links" section of the back end project.

At this point, one of the other two dlls did not appear in the Application Files section for ClickOnce. I came up with a couple of ways to fix it, but the most elegant was to add this DLL to the Reference section of the main project.

Answer 2

As indicated in How to specify which files were published using ClickOnce , change the value of the Copy Local property to the True link.

Assembly references (DLL files) are indicated as follows when adding a link: if Copy Local is False, by default it is marked as assembly of preconditions (precondition (auto)), which must be present in the GAC before the application is installed. If Copy Local is True, the default assembly is marked as the application assembly (Include (Auto)) and will be copied to the application folder during installation. The COM link will appear in the Application Files dialog box (as an .ocx file) only if the Isolate property is set to True. By default, it will be enabled.