I have a solution which produces an executable and includes approximately 8 projects which produce .dll assemblies upon which the exe is dependent. Components referenced in the dll assemblies and configured as "Copy Local" fail to show up in the bin directories when the solution is built.
It does not cause a problem when using the program on the development machine, but it does when building an install and installing on a client system. The components not explicitly included in the executable project are not copied to the bin folders and thus do not make it into the installation package.
There are references to the required projects also configured as "Copy Local".
I'm using Visual Studio 2013 with Infragistics 14.1 and creating installs with Wix Toolset v3.8
Any idea how to make these components automatically propagate up to the executable project which requires them as well in order to use the dependent assemblies?
Hello ,
What I assume that happens on your side is that your custom dlls refers Infragistics assemblies, which are installed on your deployment machine and not installed on your client machine. So along with your dlls you should deploy and Infragistics assemblies that are used of your dlls and your application. So in order to get all needed dlls in a single folder you should set “Copy Local” to all nonstandard MS references to True and you should change “Build output Path” of all of your projects (those ones that produce your dlls) to the bin folder of your application which uses them.
I hope that this will helps you.
That is close to the scenario we have going, but the custom dll's are shared by multiple applications so using that solution would require that we be able to specify multiple paths. I think that would require us to use the post build event. I'm really hoping we don't have to resort to that as it is still a manual option we have to configure in quite a few different places.
In the past Visual Studio automatically handled this for us for projects included in the solution and specified as dependencies of other projects. It actually still works for some other components we use from Component One and O2 Solutions. I'm pretty sure that it worked for the Infragistics components in the not to distant past as well.
Hello,
Our assemblies are like any other assemblies, so if it works for the other competitor then you must be missed something while build your assemblies with Infragistics dlls. Maybe you have installed version free assemblies on your client machines.
http://help.infragistics.com/Help/Doc/WinForms/2014.1/CLR4.0/html/Introduction_About_Version-Free_Assemblies.html
I am just checking about the progress of this issue. Let me know If you need my further assistance on this issue?
Thank you for using Infragistics Components.