We have several VS 2017 VB window forms desktop programs that access the QuickBooks Online API .Net SDK dlls and some of our own dlls. All have worked for years including the one in question.
In one of them we made a programming changed and updated the NuGet components and built a new .msi from the setup project.
The installed program would not run do to the wrong dlls being used. The setup dependencies is picking up the dlls from the wrong folder. Most of these dlls are brought in from nuGet. A couple of our own dlls were not but still coming from the wrong folder.
Why are the dlls in the dependencies pointing to the wrong folder? They are not the same folders as in the app's references. How
I have redone the entire project a couple of times including starting a brand new setup project but no luck.
I do use add project output when creating the setup project.
Our other apps which use the same exact dlls do not have this problem even after many updates and new msi builds.
I think that part of the issue is that are other dlls from our other projects are sometimes included in the solution for debugging. The dlls are being duplicated in the references. But are other apps also include the same other projects without an issue.